 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Airspace incursion when a navajo ATP pilot enters the dc ADIZ at 2300 ft 10 NM southeast of the ott VOR, md.
| Attributes | |
| ACN | 583772 |
| Time | |
| Date | 200306 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | navaid : ott.vortac |
| State Reference | MD |
| Altitude | msl single value : 2300 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon |
| Make Model Name | PA-31 Navajo Chieftan/Mojave/Navajo T1020 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Flight Plan | None |
| Aircraft 2 | |
| Operator | Other |
| Make Model Name | Helicopter |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : atp pilot : instrument pilot : multi engine |
| Experience | flight time last 90 days : 32.1 flight time total : 8100 flight time type : 3132 |
| ASRS Report | 583772 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : departure controller : approach |
| Events | |
| Anomaly | airspace violation : entry non adherence : far non adherence : published procedure other spatial deviation |
| Independent Detector | other flight crewb |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : investigated faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Airspace Structure Chart Or Publication Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
At approximately XX00 I departed smq, VFR, intending to pick up my IFR flight plan from new york approach control. 3 or 4 attempts were made to contact approach control on 132.8, the published frequency and the frequency used on arrival. New york approach did not answer my calls. Here is where I deviated from my planning which led to the problem. The WX was good VFR. Tailwinds were experienced on the trip to smq so I was expecting headwinds on the return. I have flown in this part of the east coast for 40 yrs and know the 'lay of the land' well. Also, the nature of my current flying is 99 percent IFR. Considering all of this, I decided to continue VFR at low altitude. I proceeded direct to mxe VOR and, after clearing the phl class B area, set up the GPS direct to ofp. Using the 'direct to' guidance, I planned to deviate as necessary to remain clear of controled and/or restr airspace. Using the GPS, the 73RD edition of the washington sectional chart and the knowledge I had about the dc ADIZ, I believed I stayed clear of all controled and/or restr airspace including the dc ADIZ. The flight proceeded to ofp and while securing the aircraft, a united states customs service helicopter landed and the officers notified me that I had penetrated the dc ADIZ. Paperwork was completed and they departed. This problem occurred because I did not have a 'clear' understanding of the boundaries of the dc ADIZ. The boundaries are not shown on the sectional chart or in the GPS database. Also, I interpreted the depiction of the washington flight restr zone boundaries to be the boundaries of the dc ADIZ. To prevent occurrences such as this, all ADIZ's should be shown on charts and included in GPS databases like other controled airspace. Since the expanded P40 and dc flight restr zone boundaries are shown on the current washington sectional, I cannot understand why the dc ADIZ is not shown.
Original NASA ASRS Text
Title: AIRSPACE INCURSION WHEN A NAVAJO ATP PLT ENTERS THE DC ADIZ AT 2300 FT 10 NM SE OF THE OTT VOR, MD.
Narrative: AT APPROX XX00 I DEPARTED SMQ, VFR, INTENDING TO PICK UP MY IFR FLT PLAN FROM NEW YORK APCH CTL. 3 OR 4 ATTEMPTS WERE MADE TO CONTACT APCH CTL ON 132.8, THE PUBLISHED FREQ AND THE FREQ USED ON ARR. NEW YORK APCH DID NOT ANSWER MY CALLS. HERE IS WHERE I DEVIATED FROM MY PLANNING WHICH LED TO THE PROB. THE WX WAS GOOD VFR. TAILWINDS WERE EXPERIENCED ON THE TRIP TO SMQ SO I WAS EXPECTING HEADWINDS ON THE RETURN. I HAVE FLOWN IN THIS PART OF THE EAST COAST FOR 40 YRS AND KNOW THE 'LAY OF THE LAND' WELL. ALSO, THE NATURE OF MY CURRENT FLYING IS 99 PERCENT IFR. CONSIDERING ALL OF THIS, I DECIDED TO CONTINUE VFR AT LOW ALT. I PROCEEDED DIRECT TO MXE VOR AND, AFTER CLRING THE PHL CLASS B AREA, SET UP THE GPS DIRECT TO OFP. USING THE 'DIRECT TO' GUIDANCE, I PLANNED TO DEVIATE AS NECESSARY TO REMAIN CLR OF CTLED AND/OR RESTR AIRSPACE. USING THE GPS, THE 73RD EDITION OF THE WASHINGTON SECTIONAL CHART AND THE KNOWLEDGE I HAD ABOUT THE DC ADIZ, I BELIEVED I STAYED CLR OF ALL CTLED AND/OR RESTR AIRSPACE INCLUDING THE DC ADIZ. THE FLT PROCEEDED TO OFP AND WHILE SECURING THE ACFT, A UNITED STATES CUSTOMS SVC HELI LANDED AND THE OFFICERS NOTIFIED ME THAT I HAD PENETRATED THE DC ADIZ. PAPERWORK WAS COMPLETED AND THEY DEPARTED. THIS PROB OCCURRED BECAUSE I DID NOT HAVE A 'CLR' UNDERSTANDING OF THE BOUNDARIES OF THE DC ADIZ. THE BOUNDARIES ARE NOT SHOWN ON THE SECTIONAL CHART OR IN THE GPS DATABASE. ALSO, I INTERPED THE DEPICTION OF THE WASHINGTON FLT RESTR ZONE BOUNDARIES TO BE THE BOUNDARIES OF THE DC ADIZ. TO PREVENT OCCURRENCES SUCH AS THIS, ALL ADIZ'S SHOULD BE SHOWN ON CHARTS AND INCLUDED IN GPS DATABASES LIKE OTHER CTLED AIRSPACE. SINCE THE EXPANDED P40 AND DC FLT RESTR ZONE BOUNDARIES ARE SHOWN ON THE CURRENT WASHINGTON SECTIONAL, I CANNOT UNDERSTAND WHY THE DC ADIZ IS NOT SHOWN.
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.