![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 637673 |
| Time | |
| Date | 200411 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | special use airspace : dcadiz.othersua |
| State Reference | VA |
| Altitude | msl single value : 1000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | general aviation : personal |
| Make Model Name | Skylane 182/RG Turbo Skylane/RG |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | other other |
| Flight Phase | climbout : initial |
| Flight Plan | None |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : multi engine pilot : commercial pilot : atp pilot : instrument |
| Experience | flight time last 90 days : 95 flight time total : 10000 flight time type : 500 |
| ASRS Report | 637673 |
| Person 2 | |
| Affiliation | government : faa |
| Function | oversight : supervisor |
| 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 | Airspace Structure Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I flew a C182T from chesterfield, va, on business. The trip was to locations in PA, wv, and va. After a leg from hyo, va, to rmn airport, I was asked to contact the washington TRACON. During this call, I was asked about my last airport of departure and notified I may have violated the airspace around washington, dc. I explained that I didn't believe I had violated any airspace and immediately reviewed the flight planning briefing notes I accumulated prior to this trip. My scan of this document which is estimated to have been over 20 pages, received from the computer based briefing, indicated to me that I had not violated any ATC or far requirements. My thoughts at that time were that the severe restrs for ATC control applied to reagan nation, washington dulles, and a few airports in maryland. A careful study of these notes indicate to me now that I was wrong. In summary, I have significant aviation experience and an aircraft that is extremely well equipped. I thought I had reviewed all available information for the flts I conducted. I conducted the flts safely in an effort to comply with my understanding of the flight restrs implied by the published information. Regardless, I evidently made a mistake by not filing and flying a VFR or IFR flight plan.
Original NASA ASRS Text
Title: PLT OF C182 ENTERS AND OPERATES WITHIN THE DC ADIZ WITHOUT AUTH.
Narrative: I FLEW A C182T FROM CHESTERFIELD, VA, ON BUSINESS. THE TRIP WAS TO LOCATIONS IN PA, WV, AND VA. AFTER A LEG FROM HYO, VA, TO RMN ARPT, I WAS ASKED TO CONTACT THE WASHINGTON TRACON. DURING THIS CALL, I WAS ASKED ABOUT MY LAST ARPT OF DEP AND NOTIFIED I MAY HAVE VIOLATED THE AIRSPACE AROUND WASHINGTON, DC. I EXPLAINED THAT I DIDN'T BELIEVE I HAD VIOLATED ANY AIRSPACE AND IMMEDIATELY REVIEWED THE FLT PLANNING BRIEFING NOTES I ACCUMULATED PRIOR TO THIS TRIP. MY SCAN OF THIS DOCUMENT WHICH IS ESTIMATED TO HAVE BEEN OVER 20 PAGES, RECEIVED FROM THE COMPUTER BASED BRIEFING, INDICATED TO ME THAT I HAD NOT VIOLATED ANY ATC OR FAR REQUIREMENTS. MY THOUGHTS AT THAT TIME WERE THAT THE SEVERE RESTRS FOR ATC CTL APPLIED TO REAGAN NATION, WASHINGTON DULLES, AND A FEW ARPTS IN MARYLAND. A CAREFUL STUDY OF THESE NOTES INDICATE TO ME NOW THAT I WAS WRONG. IN SUMMARY, I HAVE SIGNIFICANT AVIATION EXPERIENCE AND AN ACFT THAT IS EXTREMELY WELL EQUIPPED. I THOUGHT I HAD REVIEWED ALL AVAILABLE INFO FOR THE FLTS I CONDUCTED. I CONDUCTED THE FLTS SAFELY IN AN EFFORT TO COMPLY WITH MY UNDERSTANDING OF THE FLT RESTRS IMPLIED BY THE PUBLISHED INFO. REGARDLESS, I EVIDENTLY MADE A MISTAKE BY NOT FILING AND FLYING A VFR OR IFR FLT PLAN.
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.