37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 579150 |
Time | |
Date | 200304 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : jfk.vor |
State Reference | NY |
Altitude | msl single value : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny.artcc tracon : n90.tracon |
Operator | general aviation : personal |
Make Model Name | PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Plan | DVR |
Aircraft 2 | |
Navigation In Use | other vortac |
Flight Phase | cruise : level |
Route In Use | enroute : on vectors |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : student |
Experience | flight time last 90 days : 48 flight time total : 73.2 flight time type : 73.2 |
ASRS Report | 579150 |
Person 2 | |
Affiliation | government : faa |
Function | controller : flight data |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance Airspace Structure |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Pilot Deviation |
Situations | |
ATC Facility | computer equipment : n90.tracon |
Narrative:
I filed an ADIZ flight plan from huo VOR to teb with FSS. Once I took off from mgj, I switched to the FSS frequency. There was no reply. I then switched to ny center prior to entering the ny ADIZ. They responded that they had no flight plan on file. They told me to contact FSS to re-file. Again, no response. I contacted ny center again. I explained my situation concerning a lost filed flight plan. At this point, I had been circling outside the ADIZ. Then ny center issued me a squawk code, and tells me to fly a heading of 140 degrees. I had entered the ny ADIZ from the northwest once I confirmed that I was cleared to proceed into the ADIZ. I was switched to my third ny approach frequency. They asked me why I was heading away from the airport and that I was in violation of the ADIZ. I explained to them that I was vectored by the prior ny approach frequency. They then told me to proceed direct teb. Once on the ground, I was instructed to call ny TRACON. They told me what they believed I did and to never let it happen again. The teb FSDO contacted me five days later, to inquire about the deviation. As instructed I was on a beacon code, and in contact with ATC. I stated that it was a clear VFR day. All ny ctrs I contacted were extremely busy. It was difficult to get a word in edgewise. However, I received a beacon code prior to entering the ny ADIZ, somewhere between filing an ADIZ flight plan and contacting ny center, my flight plan was lost. This is not the first time it had happened. Other occurrences happened while I had my instructor with me, and he showed me, and taught me how to re-file in the air, and how to talk to ny approach and departure. The re-occurring problem is that the FSS and ny ctrs are overworked and occasionally 'lose' flight plans. Ny frequencies often don't relay the right message to each other, and are always asking the same questions the prior frequency asked. All information they request is on a flight plan...somewhere.
Original NASA ASRS Text
Title: PA28 PLT ADVISED, AFTER LNDG TEB TO CALL AND DISCUSS NY ADIZ VIOLATION. AFTER LATER DISCUSSION WITH FSDO, PLT ALLEGES RTE DEV AT DIRECTION OF ATC.
Narrative: I FILED AN ADIZ FLT PLAN FROM HUO VOR TO TEB WITH FSS. ONCE I TOOK OFF FROM MGJ, I SWITCHED TO THE FSS FREQUENCY. THERE WAS NO REPLY. I THEN SWITCHED TO NY CTR PRIOR TO ENTERING THE NY ADIZ. THEY RESPONDED THAT THEY HAD NO FLT PLAN ON FILE. THEY TOLD ME TO CONTACT FSS TO RE-FILE. AGAIN, NO RESPONSE. I CONTACTED NY CTR AGAIN. I EXPLAINED MY SIT CONCERNING A LOST FILED FLT PLAN. AT THIS POINT, I HAD BEEN CIRCLING OUTSIDE THE ADIZ. THEN NY CTR ISSUED ME A SQUAWK CODE, AND TELLS ME TO FLY A HDG OF 140 DEGS. I HAD ENTERED THE NY ADIZ FROM THE NW ONCE I CONFIRMED THAT I WAS CLRED TO PROCEED INTO THE ADIZ. I WAS SWITCHED TO MY THIRD NY APCH FREQUENCY. THEY ASKED ME WHY I WAS HDG AWAY FROM THE ARPT AND THAT I WAS IN VIOLATION OF THE ADIZ. I EXPLAINED TO THEM THAT I WAS VECTORED BY THE PRIOR NY APCH FREQUENCY. THEY THEN TOLD ME TO PROCEED DIRECT TEB. ONCE ON THE GND, I WAS INSTRUCTED TO CALL NY TRACON. THEY TOLD ME WHAT THEY BELIEVED I DID AND TO NEVER LET IT HAPPEN AGAIN. THE TEB FSDO CONTACTED ME FIVE DAYS LATER, TO INQUIRE ABOUT THE DEVIATION. AS INSTRUCTED I WAS ON A BEACON CODE, AND IN CONTACT WITH ATC. I STATED THAT IT WAS A CLR VFR DAY. ALL NY CTRS I CONTACTED WERE EXTREMELY BUSY. IT WAS DIFFICULT TO GET A WORD IN EDGEWISE. HOWEVER, I RECEIVED A BEACON CODE PRIOR TO ENTERING THE NY ADIZ, SOMEWHERE BETWEEN FILING AN ADIZ FLT PLAN AND CONTACTING NY CTR, MY FLT PLAN WAS LOST. THIS IS NOT THE FIRST TIME IT HAD HAPPENED. OTHER OCCURRENCES HAPPENED WHILE I HAD MY INSTRUCTOR WITH ME, AND HE SHOWED ME, AND TAUGHT ME HOW TO RE-FILE IN THE AIR, AND HOW TO TALK TO NY APCH AND DEP. THE RE-OCCURRING PROB IS THAT THE FSS AND NY CTRS ARE OVERWORKED AND OCCASIONALLY 'LOSE' FLT PLANS. NY FREQUENCIES OFTEN DON'T RELAY THE RIGHT MESSAGE TO EACH OTHER, AND ARE ALWAYS ASKING THE SAME QUESTIONS THE PRIOR FREQUENCY ASKED. ALL INFO THEY REQUEST IS ON A FLT PLAN...SOMEWHERE.
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.