37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 581733 |
Time | |
Date | 200305 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : iad.airport |
State Reference | VA |
Altitude | msl single value : 2700 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon tower : vps.tower |
Operator | general aviation : personal |
Make Model Name | PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 25 flight time total : 1580 flight time type : 1400 |
ASRS Report | 581733 |
Person 2 | |
Affiliation | other |
Function | observation : observer |
Events | |
Anomaly | aircraft equipment problem : less severe airspace violation : entry inflight encounter : weather inflight encounter other other anomaly other |
Independent Detector | atc equipment other atc equipment : radar other other : 2 |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airspace Structure |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I departed 58N VFR with flight following to fdk, where I stopped for fuel. My destination was eqy, around 300 NM to the southwest. Although I always prefer to use flight following on this occasion the head wind reported at my usual cruising altitudes (6 to 12000 ft) was 45 to over 60 KTS, so I elected to stay less than 3000 ft MSL until terrain required a higher altitude. Often at these lower altitudes, ATC is unable to provide radar service so I did not plan to call them until I was at a higher altitude. I knew that there were additional flight restrs in the area of washington dc (ADIZ) and consulted my current VFR sectional to avoid violating their airspace. Although my sectional described up to 15 NM restrs from the washington VOR, I knew from my briefings that day (and other recent trips along the same route), that this was extended to 30 NM. I believe I had carefully planned to remain more than 30 NM from the VOR. I departed VFR without attempting to obtain flight following and used my recently installed GPS to avoid the class B airspace. My plane has dual communications, one with a VOR receiver. On the flight from 58N to fdk, harrisburg approach informed me that my #1 radio was hard to read, though reception seemed fine. I used my #2 radio to communicate and #1 to monitor 121.5, though I was hearing only static on that frequency. I was able to receive ATIS well and thought the static I heard was from the source. Once clear of the traffic pattern and en route 15 or 20 mins, I decided to try to determine if my #2 radio also received static on 121.5. I was shocked to hear that the transmission on guard seemed to be directed at me and immediately followed their command to fly west, away from the dc area. Contributing factors: my misinterpretation of the boundaries of the ADIZ. My sense of not being in violation as I had done this trip a number of times without incident (but always with flight following). Failure to file a flight plan. Malfunction of #1 radio, initially unrecognized. Corrective actions: a more thorough review of airspace and flight planning and correction of all factors above. Perhaps the VFR sectional should be more clear in a warning regarding the ADIZ.
Original NASA ASRS Text
Title: PA28 PLT ENTERED DC ADIZ WITHOUT CLRNC OR A DISCRETE XPONDER CODE.
Narrative: I DEPARTED 58N VFR WITH FLT FOLLOWING TO FDK, WHERE I STOPPED FOR FUEL. MY DEST WAS EQY, AROUND 300 NM TO THE SW. ALTHOUGH I ALWAYS PREFER TO USE FLT FOLLOWING ON THIS OCCASION THE HEAD WIND RPTED AT MY USUAL CRUISING ALTS (6 TO 12000 FT) WAS 45 TO OVER 60 KTS, SO I ELECTED TO STAY LESS THAN 3000 FT MSL UNTIL TERRAIN REQUIRED A HIGHER ALT. OFTEN AT THESE LOWER ALTS, ATC IS UNABLE TO PROVIDE RADAR SERVICE SO I DID NOT PLAN TO CALL THEM UNTIL I WAS AT A HIGHER ALT. I KNEW THAT THERE WERE ADDITIONAL FLT RESTRS IN THE AREA OF WASHINGTON DC (ADIZ) AND CONSULTED MY CURRENT VFR SECTIONAL TO AVOID VIOLATING THEIR AIRSPACE. ALTHOUGH MY SECTIONAL DESCRIBED UP TO 15 NM RESTRS FROM THE WASHINGTON VOR, I KNEW FROM MY BRIEFINGS THAT DAY (AND OTHER RECENT TRIPS ALONG THE SAME ROUTE), THAT THIS WAS EXTENDED TO 30 NM. I BELIEVE I HAD CAREFULLY PLANNED TO REMAIN MORE THAN 30 NM FROM THE VOR. I DEPARTED VFR WITHOUT ATTEMPTING TO OBTAIN FLT FOLLOWING AND USED MY RECENTLY INSTALLED GPS TO AVOID THE CLASS B AIRSPACE. MY PLANE HAS DUAL COMS, ONE WITH A VOR RECEIVER. ON THE FLT FROM 58N TO FDK, HARRISBURG APCH INFORMED ME THAT MY #1 RADIO WAS HARD TO READ, THOUGH RECEPTION SEEMED FINE. I USED MY #2 RADIO TO COMMUNICATE AND #1 TO MONITOR 121.5, THOUGH I WAS HEARING ONLY STATIC ON THAT FREQUENCY. I WAS ABLE TO RECEIVE ATIS WELL AND THOUGHT THE STATIC I HEARD WAS FROM THE SOURCE. ONCE CLR OF THE TFC PATTERN AND ENRTE 15 OR 20 MINS, I DECIDED TO TRY TO DETERMINE IF MY #2 RADIO ALSO RECEIVED STATIC ON 121.5. I WAS SHOCKED TO HEAR THAT THE XMISSION ON GUARD SEEMED TO BE DIRECTED AT ME AND IMMEDIATELY FOLLOWED THEIR COMMAND TO FLY W, AWAY FROM THE DC AREA. CONTRIBUTING FACTORS: MY MISINTERPRETATION OF THE BOUNDARIES OF THE ADIZ. MY SENSE OF NOT BEING IN VIOLATION AS I HAD DONE THIS TRIP A NUMBER OF TIMES WITHOUT INCIDENT (BUT ALWAYS WITH FLT FOLLOWING). FAILURE TO FILE A FLT PLAN. MALFUNCTION OF #1 RADIO, INITIALLY UNRECOGNIZED. CORRECTIVE ACTIONS: A MORE THOROUGH REVIEW OF AIRSPACE AND FLT PLANNING AND CORRECTION OF ALL FACTORS ABOVE. PERHAPS THE VFR SECTIONAL SHOULD BE MORE CLR IN A WARNING REGARDING THE ADIZ.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.