37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 589274 |
Time | |
Date | 200307 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
State Reference | VA |
Altitude | msl single value : 3500 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
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 pilot : private |
Experience | flight time last 90 days : 61 flight time total : 409.3 flight time type : 61 |
ASRS Report | 589274 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
Independent Detector | other controllera |
Resolutory Action | controller : issued advisory controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew faa : assigned or threatened penalties |
Supplementary | |
Problem Areas | Flight Crew Human Performance FAA Chart Or Publication ATC Human Performance Airspace Structure |
Primary Problem | Airspace Structure |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airspace Structure | special use : dcadiz.othersua |
Narrative:
The flight departed hummel (W75) approximately XA30 under VMC. We decided to return to hef by navigating up the potomac river, with the intent of contacting potomac approach for clearance into the ADIZ as we approached the brooke VOR (brv). During the entire return trip we were monitoring the emergency 'guard' frequency as requested of all VFR flts. We heard no warnings to any aircraft about pending airspace violations. At approximately XB00, we radioed potomac approach, gave our location as 8 mi northeast of brv, and requested a squawk code and clearance into the ADIZ to hef. He gave me a code and asked me to identify. The controller then said I should have contacted them sooner, and that I was already 5 mi into the ADIZ. I expressed surprise, saying I was still well south of quantico (nyg) and the class B airspace. He indicated the ADIZ extended south of the class B airspace in that area. I asked if I should exit the airspace, but he told me to proceed to my destination and gave me a phone number to call upon my arrival. The flight terminated at approximately XB15 at hef, and I contacted the potomac TRACON by phone. I had a lengthy discussion with the controller about the dimensions and boundaries of the ADIZ, and he informed me that I had actually entered the ADIZ near (ndy), exited it as I proceeded west along the river's course, then re-entered it as I turned north toward hef. He indicated that he was required to file a report on the incident, and that the flight standards office of the FAA would contact me. This incident occurred as a result of my not being familiar with the confign of the ADIZ in this area. All of my pervious flts since the ADIZ was instituted departed to or arrived from the southwest, west, northwest or northeast. In fact, throughout the area of my incursion, the ADIZ is not coincident with the class B airspace, and due to its 'temporary' nature, it is not included on any charts or in any navigation system. I fully understand my responsibility to be fully informed about all aspects of the flight I was undertaking, but I believe that the confusing confign of the ADIZ, particularly not being coincident with any airspace that can be idented on a published chart, was a contributing factor. In the future I will ensure that I am more completely briefed prior to my departure.
Original NASA ASRS Text
Title: PLT OF C172, LACKING ADIZ CLRNC OR CODE, ENTERED DC ADIZ IN THE SOUTHERN PORTION WHICH IS NOT COINCIDENT WITH THE LATERAL EXTENT OF THE CLASS B AIRSPACE.
Narrative: THE FLT DEPARTED HUMMEL (W75) APPROX XA30 UNDER VMC. WE DECIDED TO RETURN TO HEF BY NAVING UP THE POTOMAC RIVER, WITH THE INTENT OF CONTACTING POTOMAC APCH FOR CLRNC INTO THE ADIZ AS WE APCHED THE BROOKE VOR (BRV). DURING THE ENTIRE RETURN TRIP WE WERE MONITORING THE EMER 'GUARD' FREQ AS REQUESTED OF ALL VFR FLTS. WE HEARD NO WARNINGS TO ANY ACFT ABOUT PENDING AIRSPACE VIOLATIONS. AT APPROX XB00, WE RADIOED POTOMAC APCH, GAVE OUR LOCATION AS 8 MI NE OF BRV, AND REQUESTED A SQUAWK CODE AND CLRNC INTO THE ADIZ TO HEF. HE GAVE ME A CODE AND ASKED ME TO IDENT. THE CTLR THEN SAID I SHOULD HAVE CONTACTED THEM SOONER, AND THAT I WAS ALREADY 5 MI INTO THE ADIZ. I EXPRESSED SURPRISE, SAYING I WAS STILL WELL S OF QUANTICO (NYG) AND THE CLASS B AIRSPACE. HE INDICATED THE ADIZ EXTENDED S OF THE CLASS B AIRSPACE IN THAT AREA. I ASKED IF I SHOULD EXIT THE AIRSPACE, BUT HE TOLD ME TO PROCEED TO MY DEST AND GAVE ME A PHONE NUMBER TO CALL UPON MY ARR. THE FLT TERMINATED AT APPROX XB15 AT HEF, AND I CONTACTED THE POTOMAC TRACON BY PHONE. I HAD A LENGTHY DISCUSSION WITH THE CTLR ABOUT THE DIMENSIONS AND BOUNDARIES OF THE ADIZ, AND HE INFORMED ME THAT I HAD ACTUALLY ENTERED THE ADIZ NEAR (NDY), EXITED IT AS I PROCEEDED W ALONG THE RIVER'S COURSE, THEN RE-ENTERED IT AS I TURNED N TOWARD HEF. HE INDICATED THAT HE WAS REQUIRED TO FILE A RPT ON THE INCIDENT, AND THAT THE FLT STANDARDS OFFICE OF THE FAA WOULD CONTACT ME. THIS INCIDENT OCCURRED AS A RESULT OF MY NOT BEING FAMILIAR WITH THE CONFIGN OF THE ADIZ IN THIS AREA. ALL OF MY PERVIOUS FLTS SINCE THE ADIZ WAS INSTITUTED DEPARTED TO OR ARRIVED FROM THE SW, W, NW OR NE. IN FACT, THROUGHOUT THE AREA OF MY INCURSION, THE ADIZ IS NOT COINCIDENT WITH THE CLASS B AIRSPACE, AND DUE TO ITS 'TEMPORARY' NATURE, IT IS NOT INCLUDED ON ANY CHARTS OR IN ANY NAV SYS. I FULLY UNDERSTAND MY RESPONSIBILITY TO BE FULLY INFORMED ABOUT ALL ASPECTS OF THE FLT I WAS UNDERTAKING, BUT I BELIEVE THAT THE CONFUSING CONFIGN OF THE ADIZ, PARTICULARLY NOT BEING COINCIDENT WITH ANY AIRSPACE THAT CAN BE IDENTED ON A PUBLISHED CHART, WAS A CONTRIBUTING FACTOR. IN THE FUTURE I WILL ENSURE THAT I AM MORE COMPLETELY BRIEFED PRIOR TO MY DEP.
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.