|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||atc facility : ftw|
|Controlling Facilities||tower : ftw|
tower : fwh
|Operator||general aviation : personal|
|Make Model Name||Small Aircraft, Low Wing, 1 Eng, Fixed Gear|
|Flight Phase||cruise other|
|Function||flight crew : single pilot|
|Qualification||pilot : private|
|Experience||flight time last 90 days : 45|
flight time total : 3780
flight time type : 460
|Anomaly||other anomaly other|
other anomaly other
|Independent Detector||other flight crewa|
|Resolutory Action||flight crew : exited penetrated airspace|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
Recently 2 instances have shown me a deficiency in the ATC system that can trap a pilot into flying into an air traffic area even though he is using ATC for flight following or trying to contact the appropriate tower. In first instance, on a flight from the south to meacham field to north of meacham field, I tried regl approach for flight following. Due to low altitude, they did not pick up the transponder, so I went to meacham field tower for clearance through their air traffic area. Even though I was in meacham's air traffic area, I was also in carswell's air traffic area. I am sure each has areas of responsibilities, but a transit pilot has no way of knowing what they are since they are not depicted on the maps. If the control zone depiction is accurate to their areas of responsibility, then I was correct on meacham tower, even though actually I was closer to carswell tower. On the other occasion, regl approach descended me apparently through meacham tower's air traffic area. There are several places where air traffic area's overlap, and local internal agreements control areas of responsibility, but it is impossible for transient pilots to know these local agreements. A much safer operation could be had if pilots knew whose airspace they were in and which control facility to contact. To help pilots who are trying to use the system, air traffic area responsibility areas should be depicted on the maps when it is not standard or air traffic area's should be aligned with the control zones so as a minimum the control zones mirror each tower's area of responsibility.
Original NASA ASRS Text
Title: UNAUTH PENETRATION ATA.
Narrative: RECENTLY 2 INSTANCES HAVE SHOWN ME A DEFICIENCY IN THE ATC SYS THAT CAN TRAP A PLT INTO FLYING INTO AN ATA EVEN THOUGH HE IS USING ATC FOR FLT FOLLOWING OR TRYING TO CONTACT THE APPROPRIATE TWR. IN FIRST INSTANCE, ON A FLT FROM THE S TO MEACHAM FIELD TO N OF MEACHAM FIELD, I TRIED REGL APCH FOR FLT FOLLOWING. DUE TO LOW ALT, THEY DID NOT PICK UP THE TRANSPONDER, SO I WENT TO MEACHAM FIELD TWR FOR CLRNC THROUGH THEIR ATA. EVEN THOUGH I WAS IN MEACHAM'S ATA, I WAS ALSO IN CARSWELL'S ATA. I AM SURE EACH HAS AREAS OF RESPONSIBILITIES, BUT A TRANSIT PLT HAS NO WAY OF KNOWING WHAT THEY ARE SINCE THEY ARE NOT DEPICTED ON THE MAPS. IF THE CTL ZONE DEPICTION IS ACCURATE TO THEIR AREAS OF RESPONSIBILITY, THEN I WAS CORRECT ON MEACHAM TWR, EVEN THOUGH ACTUALLY I WAS CLOSER TO CARSWELL TWR. ON THE OTHER OCCASION, REGL APCH DSNDED ME APPARENTLY THROUGH MEACHAM TWR'S ATA. THERE ARE SEVERAL PLACES WHERE ATA'S OVERLAP, AND LCL INTERNAL AGREEMENTS CTL AREAS OF RESPONSIBILITY, BUT IT IS IMPOSSIBLE FOR TRANSIENT PLTS TO KNOW THESE LCL AGREEMENTS. A MUCH SAFER OPERATION COULD BE HAD IF PLTS KNEW WHOSE AIRSPACE THEY WERE IN AND WHICH CTL FAC TO CONTACT. TO HELP PLTS WHO ARE TRYING TO USE THE SYS, ATA RESPONSIBILITY AREAS SHOULD BE DEPICTED ON THE MAPS WHEN IT IS NOT STANDARD OR ATA'S SHOULD BE ALIGNED WITH THE CTL ZONES SO AS A MINIMUM THE CTL ZONES MIRROR EACH TWR'S AREA OF RESPONSIBILITY.
Data retrieved from NASA's ASRS site as of August 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.