> On Feb 7, 2:19 pm, Dave Nadler <d...@nadler.com> wrote:
> > Reminders from the SSF/SSA safety briefing at Reno:
> > (1) The 1202 transponder code for gliders is effective
> > nationwide this week. Do contact your local ATC and
> > make sure they are expecting this...
> > (2) Do NOT press IDENT unless specifically requested
> > to do so by ATC.
> > Lets all be good neighbors out there,
> > Thanks,
> > Best Regards, Dave "YO electric"- Hide quoted text -
> - Show quoted text -
Dave:
I went to the FAA web site to look for the new order which should be
JO 7110.66E, but found nothing but the old order (just subtract one
letter from the end of the one I've just mentioned.) One would think
that the Feds would have the current order posted along with the
effective date. On the other hand they may be waiting until Feb. 9 to
make it available on the internet to the un-washed masses.
I'll check again after that date.
Apologies, I'm repeating what was briefed,
but I did not get the relevant publication ID.
It would be great if anybody can find it...
Effective date is 9-February.
Thanks,
Best Regards, Dave
On Feb 8, 7:36 am, Dave Nadler <d...@nadler.com> wrote:
> Apologies, I'm repeating what was briefed,
> but I did not get the relevant publication ID.
> It would be great if anybody can find it...
> Effective date is 9-February.
> Thanks,
> Best Regards, Dave
We have received confirmation from Tucson TRACON to change our
dedicated glider transponder code from the present 0400 to the new
National 1202 on February 9th. Our President asked for this
confirmation from them, but they have obviously been informed.
I was shown a set of initial documentation changes back in May 2011. Don't
know if the final changes were similar. I'd be happy to send anyone a .pdf
copy of those changes. Email me at rick dot fuller at cox dot net for a
copy.
>I went to the FAA web site to look for the new order which should be
>JO 7110.66E, but found nothing but the old order (just subtract one
>letter from the end of the one I've just mentioned.) One would think
>that the Feds would have the current order posted along with the
>effective date. On the other hand they may be waiting until Feb. 9 to
>make it available on the internet to the un-washed masses.
>I'll check again after that date.
> I was shown a set of initial documentation changes back in May 2011. Don't
> know if the final changes were similar. I'd be happy to send anyone a .pdf
> copy of those changes. Email me at rick dot fuller at cox dot net for a
> copy.
> Rick "CL"
> >Dave:
> >I went to the FAA web site to look for the new order which should be
> >JO 7110.66E, but found nothing but the old order (just subtract one
> >letter from the end of the one I've just mentioned.) One would think
> >that the Feds would have the current order posted along with the
> >effective date. On the other hand they may be waiting until Feb. 9 to
> >make it available on the internet to the un-washed masses.
> >I'll check again after that date.
> >Zulu- Hide quoted text -
> - Show quoted text -
On 2 Feb 2012, Notice JO7110.577 was signed out by the FAA informing
all ATC facilities to monitor the 1202 Glider Code, effective on 7
March 2012.
I could only find 7110.66D which lists the 1201 code for gliders.
There is an internal FAA Change Notice Document dated May 2011 to
change AIM, FARs and 7110.65 plus other FAA Documnets to the 1202
code, effective 9 Feb 2012.
The change will be an added note in AIM par 4-1-20, and a change in
order 7110.65U par 5-2-13 (added code 1202 to be monitored by ATC),
and par 5-2-9 (very decent description of glider-unique operational
characteristics!). Publication date July 26, 2012 (the next AIM cycle
- may explain the cancellation of the notice in force until then).
The hope is that Air Traffic Automation can be updated in the future
to incorporate a “G” into the datablock to signify a glider.
The TSO efforts for a low-cost/low-power ADS-B transceiver are also
moving along.
On Feb 8, 7:14 pm, Kolie <losmyuit-gro...@usa.net> wrote:
> The change will be an added note in AIM par 4-1-20, and a change in
> order 7110.65U par 5-2-13 (added code 1202 to be monitored by ATC),
> and par 5-2-9 (very decent description of glider-unique operational
> characteristics!). Publication date July 26, 2012 (the next AIM cycle
> - may explain the cancellation of the notice in force until then).
> The hope is that Air Traffic Automation can be updated in the future
> to incorporate a “G” into the datablock to signify a glider.
> The TSO efforts for a low-cost/low-power ADS-B transceiver are also
> moving along.
> KL
That may explain some of the issues. FAA cannot even meet their own
internal suspense and publication dates. So now a temporary JO
notification telling the controllers what 1202 is all about and to
program their radar display filters to show 1202 codes.
I just checked all of the publications listed in the Internal Change
Memo I mentioned and none of the online documents, with change
publication dates of 9 Feb 2012 have anything to say about the 1202
Code and Gliders.
I did get an email this evening from my local TRACON Airspace manager,
forwarding me the 7110.577 document and wanting to discuss the impact
to our local soaring operations. I replied, we are ready to roll from
1200 to 1202, was he ready? We have about 6 gliders in the local area
with transponders installed.
> I did get an email this evening from my local TRACON Airspace manager,
> forwarding me the 7110.577 document and wanting to discuss the impact
> to our local soaring operations. I replied, we are ready to roll from
> 1200 to 1202, was he ready?
Does anyone know if they will issue NOTAMS as these changes are implemented?
-- Eric Greenwell - Washington State, USA (change ".netto" to ".us" to email me)
- "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarm http://tinyurl.com/yb3xywl
On Feb 8, 8:50 pm, Eric Greenwell <ow...@thegreenwells.netto> wrote:
> On 2/8/2012 7:37 PM, T wrote:
> > I did get an email this evening from my local TRACON Airspace manager,
> > forwarding me the 7110.577 document and wanting to discuss the impact
> > to our local soaring operations. I replied, we are ready to roll from
> > 1200 to 1202, was he ready?
> Does anyone know if they will issue NOTAMS as these changes are implemented?
> --
> Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
> email me)
> - "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarmhttp://tinyurl.com/yb3xywl
ZDV Airspace Beacons and Procedures said to hold off on 1202 until the
effective date of March 7th.
> On Feb 8, 8:50 pm, Eric Greenwell <ow...@thegreenwells.netto> wrote:
> > On 2/8/2012 7:37 PM, T wrote:
> > > I did get an email this evening from my local TRACON Airspace manager,
> > > forwarding me the 7110.577 document and wanting to discuss the impact
> > > to our local soaring operations. I replied, we are ready to roll from
> > > 1200 to 1202, was he ready?
> > Does anyone know if they will issue NOTAMS as these changes are implemented?
> > --
> > Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
> > email me)
> > - "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarmhttp://tinyurl.com/yb3xywl
> ZDV Airspace Beacons and Procedures said to hold off on 1202 until the
> effective date of March 7th.
> Frank Whiteley
Another pilot forwarded me a copy of a proposed change/briefing
sheet. The proposed change did not make it into 7110.65U which became
effective Feb 9, 2012, hence JO 7110.577, delaying implementation
until March 7.
> On Feb 8, 8:50 pm, Eric Greenwell <ow...@thegreenwells.netto> wrote:
> > On 2/8/2012 7:37 PM, T wrote:
> > > I did get an email this evening from my local TRACON Airspace manager,
> > > forwarding me the 7110.577 document and wanting to discuss the impact
> > > to our local soaring operations. I replied, we are ready to roll from
> > > 1200 to 1202, was he ready?
> > Does anyone know if they will issue NOTAMS as these changes are implemented?
> > --
> > Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
> > email me)
> > - "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarmhttp://tinyurl.com/yb3xywl
> ZDV Airspace Beacons and Procedures said to hold off on 1202 until the
> effective date of March 7th.
> Frank Whiteley
I think part of the delay is due to 7110.66E not having been published
yet (national beacon/code assignments), which is why the change was
omitted from 7110.65U.
>On Feb 9, 9:01=A0am, Frank Whiteley wrote:
>> On Feb 8, 8:50=A0pm, Eric Greenwell wrote:
>> > On 2/8/2012 7:37 PM, T wrote:
>> > > I did get an email this evening from my local TRACON Airspace
>manager=
>,
>> > > forwarding me the 7110.577 document and wanting to discuss the impact
>> > > to our local soaring operations. I replied, we are ready to roll
from
>> > > 1200 to 1202, was he ready?
>> > Does anyone know if they will issue NOTAMS as these changes are
>impleme=
>nted?
>> > --
>> > Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
>> > email me)
>> > - "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS,
>Flarmhttp:/=
>/tinyurl.com/yb3xywl
>> ZDV Airspace Beacons and Procedures said to hold off on 1202 until the
>> effective date of March 7th.
>> Frank Whiteley
>I think part of the delay is due to 7110.66E not having been published
>yet (national beacon/code assignments), which is why the change was
>omitted from 7110.65U.
