37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 583880 |
Time | |
Date | 200306 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : csn.vortac |
State Reference | VA |
Altitude | msl single value : 2400 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon tower : ont.tower |
Operator | general aviation : personal |
Make Model Name | M-20 B/C Ranger |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument |
Experience | flight time last 90 days : 5.2 flight time total : 248.4 flight time type : 248.4 |
ASRS Report | 583880 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach controller : departure other personnel other |
Events | |
Anomaly | airspace violation : entry non adherence : far non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After a VFR flight from mrb to 9w7, I received a cell phone call from a 'security coordinator,' who said I had penetrated the edge of the dc ADIZ and wanted to know if I was aware of the existence and procedures pertaining to that airspace. I am very much aware of the dc ADIZ and the procedures pertaining to it. I spent considerable time reviewing the 27 pages of NOTAM information prior to this flight, including NOTAM 3/2126 (previously missing text). It was not my intention to operate within the dc ADIZ. Since it was a beautiful, clear day, and there have been so few in the recent months, I planned to execute the flight according to VFR requirements outside that zone. Problems: the published navigation charts from the united states government do not include any data pertaining to this ADIZ, as they do with all other ADIZ. My planned flight path was to avoid the 'dc tri-area' class B airspace, and thereby also avoid the ADIZ (although pass very close to it). If the government had issued charts with the airspace included, there would be no confusion about the location of the boundary relative to clearly identifiable landmarks, and radio navigation facilities. According to my observation of clearly visible landmarks during the flight, and flight instruments, I was outside the class B airspace, and the ADIZ. The wording of the NOTAM is not as clear as it could have been. The FAA has ignored comments suggesting language that is more succinct to define the zone, and to define the procedure. Additionally, the absence of any official published navigation charts including this space has increased the probability of problems with this space. Suggestions: the FAA should immediately update and publish all applicable navigation charts. The FAA should issue a NOTAM indicating the issuance of the newly published charts. Both pilots and controllers should be operating from a single source of official information, not data interpolated from less than clear language, where multiple interpolations take effect to define space.
Original NASA ASRS Text
Title: A VERY LOW TIME M20 PLT RPTED THAT HE WAS CONTACTED BY PCT AFTER VIOLATING THE DC ADIZ.
Narrative: AFTER A VFR FLT FROM MRB TO 9W7, I RECEIVED A CELL PHONE CALL FROM A 'SECURITY COORDINATOR,' WHO SAID I HAD PENETRATED THE EDGE OF THE DC ADIZ AND WANTED TO KNOW IF I WAS AWARE OF THE EXISTENCE AND PROCS PERTAINING TO THAT AIRSPACE. I AM VERY MUCH AWARE OF THE DC ADIZ AND THE PROCS PERTAINING TO IT. I SPENT CONSIDERABLE TIME REVIEWING THE 27 PAGES OF NOTAM INFO PRIOR TO THIS FLT, INCLUDING NOTAM 3/2126 (PREVIOUSLY MISSING TEXT). IT WAS NOT MY INTENTION TO OPERATE WITHIN THE DC ADIZ. SINCE IT WAS A BEAUTIFUL, CLR DAY, AND THERE HAVE BEEN SO FEW IN THE RECENT MONTHS, I PLANNED TO EXECUTE THE FLT ACCORDING TO VFR REQUIREMENTS OUTSIDE THAT ZONE. PROBS: THE PUBLISHED NAV CHARTS FROM THE UNITED STATES GOV DO NOT INCLUDE ANY DATA PERTAINING TO THIS ADIZ, AS THEY DO WITH ALL OTHER ADIZ. MY PLANNED FLT PATH WAS TO AVOID THE 'DC TRI-AREA' CLASS B AIRSPACE, AND THEREBY ALSO AVOID THE ADIZ (ALTHOUGH PASS VERY CLOSE TO IT). IF THE GOV HAD ISSUED CHARTS WITH THE AIRSPACE INCLUDED, THERE WOULD BE NO CONFUSION ABOUT THE LOCATION OF THE BOUNDARY RELATIVE TO CLRLY IDENTIFIABLE LANDMARKS, AND RADIO NAV FACILITIES. ACCORDING TO MY OBSERVATION OF CLRLY VISIBLE LANDMARKS DURING THE FLT, AND FLT INSTS, I WAS OUTSIDE THE CLASS B AIRSPACE, AND THE ADIZ. THE WORDING OF THE NOTAM IS NOT AS CLR AS IT COULD HAVE BEEN. THE FAA HAS IGNORED COMMENTS SUGGESTING LANGUAGE THAT IS MORE SUCCINCT TO DEFINE THE ZONE, AND TO DEFINE THE PROC. ADDITIONALLY, THE ABSENCE OF ANY OFFICIAL PUBLISHED NAV CHARTS INCLUDING THIS SPACE HAS INCREASED THE PROBABILITY OF PROBS WITH THIS SPACE. SUGGESTIONS: THE FAA SHOULD IMMEDIATELY UPDATE AND PUBLISH ALL APPLICABLE NAV CHARTS. THE FAA SHOULD ISSUE A NOTAM INDICATING THE ISSUANCE OF THE NEWLY PUBLISHED CHARTS. BOTH PLTS AND CTLRS SHOULD BE OPERATING FROM A SINGLE SOURCE OF OFFICIAL INFO, NOT DATA INTERPOLATED FROM LESS THAN CLR LANGUAGE, WHERE MULTIPLE INTERPOLATIONS TAKE EFFECT TO DEFINE SPACE.
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.