 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of small aircraft on an ADIZ clearance to mtn is incorrectly advised by pct he was not properly authority/authorized for operations in the dc ADIZ. Pct later advises they were in error.
| Attributes | |
| ACN | 605274 |
| Time | |
| Date | 200401 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : dca.airport |
| State Reference | DC |
| Altitude | msl single value : 4500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Flight Plan | DVR |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : atp pilot : commercial pilot : multi engine pilot : instrument |
| Experience | flight time last 90 days : 31 flight time total : 9327 flight time type : 500 |
| ASRS Report | 605274 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Events | |
| Anomaly | airspace violation : entry |
| Independent Detector | other controllera |
| Resolutory Action | none taken : unable |
| Supplementary | |
| Problem Areas | ATC Human Performance Airport Airspace Structure Environmental Factor |
| Primary Problem | ATC Human Performance |
Narrative:
While on an ADIZ flight plan south from philadelphia to richmond, controller was confused about ADIZ clearance after handoff. Previous controller had established contact with discrete code, radar contact and 2-WAY communication. Repeated communications unable to get further response and contacted martin tower with descent into their airspace. After passing through tower, tower xferred back to approach with approach having similar problems not confirming ADIZ clearance and requesting I remain clear of area when I was already in the ADIZ by previous clearance. Confusion remained with approach until landing in richmond. Contacted approach and they confirmed confusion was on their part and that I was on an ADIZ clearance flight plan and it was confusion that caused the 'remain clear' and other controller remarks. They said no further action was required on my part.
Original NASA ASRS Text
Title: PLT OF SMA ON AN ADIZ CLRNC TO MTN IS INCORRECTLY ADVISED BY PCT HE WAS NOT PROPERLY AUTH FOR OPS IN THE DC ADIZ. PCT LATER ADVISES THEY WERE IN ERROR.
Narrative: WHILE ON AN ADIZ FLT PLAN S FROM PHILADELPHIA TO RICHMOND, CTLR WAS CONFUSED ABOUT ADIZ CLRNC AFTER HDOF. PREVIOUS CTLR HAD ESTABLISHED CONTACT WITH DISCRETE CODE, RADAR CONTACT AND 2-WAY COM. REPEATED COMS UNABLE TO GET FURTHER RESPONSE AND CONTACTED MARTIN TWR WITH DSCNT INTO THEIR AIRSPACE. AFTER PASSING THROUGH TWR, TWR XFERRED BACK TO APCH WITH APCH HAVING SIMILAR PROBS NOT CONFIRMING ADIZ CLRNC AND REQUESTING I REMAIN CLR OF AREA WHEN I WAS ALREADY IN THE ADIZ BY PREVIOUS CLRNC. CONFUSION REMAINED WITH APCH UNTIL LNDG IN RICHMOND. CONTACTED APCH AND THEY CONFIRMED CONFUSION WAS ON THEIR PART AND THAT I WAS ON AN ADIZ CLRNC FLT PLAN AND IT WAS CONFUSION THAT CAUSED THE 'REMAIN CLR' AND OTHER CTLR REMARKS. THEY SAID NO FURTHER ACTION WAS REQUIRED ON MY PART.
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.