View Single Post
  #29  
Old December 29th 05, 10:35 PM posted to rec.aviation.student,rec.aviation.piloting
external usenet poster
 
Posts: n/a
Default Another ADIZ violation?

On Thu, 29 Dec 2005 18:24:58 +0000 (UTC), (Roy Smith)
wrote:

Jose wrote:
91.3 doesn't give you carte blanche to do whatever you want. It gives you
the authority to deviate from the rules *to the extent required* to deal
with the emergency.


... and a communication failure in the ADIZ is a bona fide emergency
even in circumstances which, outside the ADIZ, would be a non-event. It
may well be better to turn around and land nearby than to point the nose
outward and drone on for fifteen minutes in an unexpected direction.


It's hardly an unexpected direction, considering there's a NOTAM
instructing you to do exactly that:

!FDC 4/5555 ZDC SPECIAL NOTICE... EFFECTIVE IMMEDIATELY UNTIL
FURTHER NOTICE. PURSUANT TO 14 CFR SECTION 99.7, SPECIAL SECURITY
INSTRUCTIONS, THE FOLLOWING PROCEDURES ARE IN EFFECT:
A. ANY PERSON OPERATING AN AIRCRAFT WITHIN THE WASHINGTON, DC
METROPOLITAN AREA AIR DEFENSE IDENTIFICATION ZONE (DC ADIZ),
IMMEDIATELY UPON BECOMING AWARE OF AN INABILITY TO COMPLY WITH THE
REQUIREMENT TO CONTINUOUSLY TRANSMIT THE ATC ASSIGNED TRANSPONDER
CODE, SHALL EXIT THE DC ADIZ BY FLYING THE MOST DIRECT COURSE TO
OUTSIDE THE LATERAL LIMITS OF THE DC ADIZ.


OK, this NOTAM handles the case of no transponder, but what about no 2
way comm's?

As long as he's still squawking the code, I would think turn around
and land at nearest suitable field (squawk 7600 for a minute or two
and then go back to assigned code?) should work to remain within the
limits of both requirements. Course, I wouldn't turn *toward* the
city or FRZ, but if there's an airfield right near me?