|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||atc facility : nhk.tracon|
|Controlling Facilities||tracon : pct.tracon|
tracon : nhk.tracon
|Operator||general aviation : personal|
|Make Model Name||PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior|
|Operating Under FAR Part||Part 91|
|Navigation In Use||other|
|Flight Phase||cruise : level|
|Function||flight crew : single pilot|
|Qualification||pilot : private|
|Affiliation||government : faa|
|Function||controller : approach|
|Anomaly||airspace violation : entry|
non adherence : published procedure
non adherence : far
|Independent Detector||other controllera|
|Resolutory Action||none taken : detected after the fact|
|Consequence||faa : assigned or threatened penalties|
faa : reviewed incident with flight crew
|Problem Areas||Flight Crew Human Performance|
Chart Or Publication
ATC Human Performance
|Air Traffic Incident||Pilot Deviation|
|Airspace Structure||special use : dcadiz.othersua|
Note: 2 occurrences in same general area (aug/sat/03, sep/mon/03). While transiting the area south of dc ADIZ (route ptx-dir-rmn), I inadvertently broke the ADIZ airspace. On the wbound (aug/sat/03) leg, I had flight following from patuxent approach. On exiting passenger airspace, they informed me '...unable to hand off to potomac approach, squawk VFR...,' which I did. Controller also warned that my course would lead into dc ADIZ. I adjusted approximately 15 degrees south from 285 degrees. He said 'that will clear.' I also have a moving map connected to my GPS. This showed me to be well clear of the ADIZ. (Wrong!). I kept tight to the north of R6611 on a westerly course. Apparently, the tfr information on my map was in error (I had downloaded the current information on aug/fri/03. I am in contact with the software manufacturer to see why this happened, no response at this writing. All other information that I had showed a gap between the ADIZ and R6611. Later, I found this to be in error. I was asked to contact potomac TRACON upon landing, which I did. The supervisor could not give specific information on the 'intrusion.' on the second, I departed rmn direct brv, direct pxt. I tried to get flight following on the potomac frequency assigned for rmn. When I finally got a controller, he advised a different frequency, which I switched to. Silence on that frequency. Switched back, but could not get a response. By that time, I had already intruded on the ADIZ (again near R6611). Again, my moving map-GPS showed me to be clear of the tfr. Contacted passenger approach, got a squawk code and flight following through their airspace. While near pxt, approach notified me to contact potomac TRACON after landing '...you broke the ADIZ....' potomac approach seemed reluctant to cover VFR flight following. I said 'this is due to the lack of accepting the handoff from patuxent and the 'no response' situation.' are they overloaded? The incorrect frequency (sep/mon/03) was definitely a factor on that leg. I have checked and am in possession of correct charts (and graphics) depicting the ADIZ and will not make that mistake again!
Original NASA ASRS Text
Title: PLT OF PA28, CERTAIN OF HIS RECTITUDE BY VIRTUE OF REVIEWING CHARTS AND MONITORING HIS GPS, NONETHELESS PENETRATES THE DC ADIZ.
Narrative: NOTE: 2 OCCURRENCES IN SAME GENERAL AREA (AUG/SAT/03, SEP/MON/03). WHILE TRANSITING THE AREA S OF DC ADIZ (RTE PTX-DIR-RMN), I INADVERTENTLY BROKE THE ADIZ AIRSPACE. ON THE WBOUND (AUG/SAT/03) LEG, I HAD FLT FOLLOWING FROM PATUXENT APCH. ON EXITING PAX AIRSPACE, THEY INFORMED ME '...UNABLE TO HAND OFF TO POTOMAC APCH, SQUAWK VFR...,' WHICH I DID. CTLR ALSO WARNED THAT MY COURSE WOULD LEAD INTO DC ADIZ. I ADJUSTED APPROX 15 DEGS S FROM 285 DEGS. HE SAID 'THAT WILL CLEAR.' I ALSO HAVE A MOVING MAP CONNECTED TO MY GPS. THIS SHOWED ME TO BE WELL CLR OF THE ADIZ. (WRONG!). I KEPT TIGHT TO THE N OF R6611 ON A WESTERLY COURSE. APPARENTLY, THE TFR INFO ON MY MAP WAS IN ERROR (I HAD DOWNLOADED THE CURRENT INFO ON AUG/FRI/03. I AM IN CONTACT WITH THE SOFTWARE MANUFACTURER TO SEE WHY THIS HAPPENED, NO RESPONSE AT THIS WRITING. ALL OTHER INFO THAT I HAD SHOWED A GAP BTWN THE ADIZ AND R6611. LATER, I FOUND THIS TO BE IN ERROR. I WAS ASKED TO CONTACT POTOMAC TRACON UPON LNDG, WHICH I DID. THE SUPVR COULD NOT GIVE SPECIFIC INFO ON THE 'INTRUSION.' ON THE SECOND, I DEPARTED RMN DIRECT BRV, DIRECT PXT. I TRIED TO GET FLT FOLLOWING ON THE POTOMAC FREQ ASSIGNED FOR RMN. WHEN I FINALLY GOT A CTLR, HE ADVISED A DIFFERENT FREQ, WHICH I SWITCHED TO. SILENCE ON THAT FREQ. SWITCHED BACK, BUT COULD NOT GET A RESPONSE. BY THAT TIME, I HAD ALREADY INTRUDED ON THE ADIZ (AGAIN NEAR R6611). AGAIN, MY MOVING MAP-GPS SHOWED ME TO BE CLR OF THE TFR. CONTACTED PAX APCH, GOT A SQUAWK CODE AND FLT FOLLOWING THROUGH THEIR AIRSPACE. WHILE NEAR PXT, APCH NOTIFIED ME TO CONTACT POTOMAC TRACON AFTER LNDG '...YOU BROKE THE ADIZ....' POTOMAC APCH SEEMED RELUCTANT TO COVER VFR FLT FOLLOWING. I SAID 'THIS IS DUE TO THE LACK OF ACCEPTING THE HDOF FROM PATUXENT AND THE 'NO RESPONSE' SIT.' ARE THEY OVERLOADED? THE INCORRECT FREQ (SEP/MON/03) WAS DEFINITELY A FACTOR ON THAT LEG. I HAVE CHKED AND AM IN POSSESSION OF CORRECT CHARTS (AND GRAPHICS) DEPICTING THE ADIZ AND WILL NOT MAKE THAT MISTAKE AGAIN!
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.