37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 599008 |
Time | |
Date | 200311 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : dca.airport |
State Reference | DC |
Altitude | msl single value : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | departure : vfr |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 15 flight time total : 110 flight time type : 17 |
ASRS Report | 599008 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : far non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | flight crew : diverted to another airport flight crew : exited penetrated airspace |
Consequence | faa : assigned or threatened penalties faa : investigated faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Airspace Structure Flight Crew Human Performance FAA |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Oct/thu/03, I called FSS for a briefing and to file an ADIZ flight plan for a trip from gai to esn planned for nov/sat/03. I was given all the information in a standard flight briefing, but I don't remember ever getting information about the no fly zone surrounding washington dc (15 mi radius). That same night, I completed my flight planning for my trip. I performed the standard planning including route of flight, chkpoints, times, etc. On nov/sat/03, I contacted FSS again for an updated briefing and to request information about any flight restrs on my route of flight. I was given information regarding the WX, but like the previous conversation with FSS, I was not advised about the no fly zone. I took off from gai at XA30. Once clear of the traffic at gai (and clear of the area), I contacted potomac approach. When potomac got back to me, they said that I was in the no fly zone and I was given a number to call once I arrived at esn. Being new to the area, I was concerned that I might face additional problems with flight restr zone during the remainder of my flight and on the return. Instead of continuing to esn, I requested to go back to gai. I was given permission and I proceeded to land at gai. Once at gai, I called potomac approach. They informed me that I would be notified within 30 days for investigation. Prior to my flight, I also reviewed the latest sectional and I used that for my flight planning. The washington sectional does not clearly depict the no fly zone. Even now that I am aware of the no fly zone, I am still unable to clearly identify its boundaries. My use of the FSS services as well flight planning could not and did not allow me to avoid the area.
Original NASA ASRS Text
Title: C172 PLT WAS ACCUSED BY PCT APCH OF PENETRATING THE 'FLT RESTR ZONE (FRZ)' WITHIN DC ADIZ AS DESCRIBED IN NOTAM 3-2126.
Narrative: OCT/THU/03, I CALLED FSS FOR A BRIEFING AND TO FILE AN ADIZ FLT PLAN FOR A TRIP FROM GAI TO ESN PLANNED FOR NOV/SAT/03. I WAS GIVEN ALL THE INFO IN A STANDARD FLT BRIEFING, BUT I DON'T REMEMBER EVER GETTING INFO ABOUT THE NO FLY ZONE SURROUNDING WASHINGTON DC (15 MI RADIUS). THAT SAME NIGHT, I COMPLETED MY FLT PLANNING FOR MY TRIP. I PERFORMED THE STANDARD PLANNING INCLUDING RTE OF FLT, CHKPOINTS, TIMES, ETC. ON NOV/SAT/03, I CONTACTED FSS AGAIN FOR AN UPDATED BRIEFING AND TO REQUEST INFO ABOUT ANY FLT RESTRS ON MY RTE OF FLT. I WAS GIVEN INFO REGARDING THE WX, BUT LIKE THE PREVIOUS CONVERSATION WITH FSS, I WAS NOT ADVISED ABOUT THE NO FLY ZONE. I TOOK OFF FROM GAI AT XA30. ONCE CLR OF THE TFC AT GAI (AND CLR OF THE AREA), I CONTACTED POTOMAC APCH. WHEN POTOMAC GOT BACK TO ME, THEY SAID THAT I WAS IN THE NO FLY ZONE AND I WAS GIVEN A NUMBER TO CALL ONCE I ARRIVED AT ESN. BEING NEW TO THE AREA, I WAS CONCERNED THAT I MIGHT FACE ADDITIONAL PROBS WITH FLT RESTR ZONE DURING THE REMAINDER OF MY FLT AND ON THE RETURN. INSTEAD OF CONTINUING TO ESN, I REQUESTED TO GO BACK TO GAI. I WAS GIVEN PERMISSION AND I PROCEEDED TO LAND AT GAI. ONCE AT GAI, I CALLED POTOMAC APCH. THEY INFORMED ME THAT I WOULD BE NOTIFIED WITHIN 30 DAYS FOR INVESTIGATION. PRIOR TO MY FLT, I ALSO REVIEWED THE LATEST SECTIONAL AND I USED THAT FOR MY FLT PLANNING. THE WASHINGTON SECTIONAL DOES NOT CLRLY DEPICT THE NO FLY ZONE. EVEN NOW THAT I AM AWARE OF THE NO FLY ZONE, I AM STILL UNABLE TO CLRLY IDENT ITS BOUNDARIES. MY USE OF THE FSS SVCS AS WELL FLT PLANNING COULD NOT AND DID NOT ALLOW ME TO AVOID THE AREA.
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.