37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 574120 |
Time | |
Date | 200302 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : bwi.airport |
State Reference | MD |
Altitude | agl single value : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon tower : bur.tower |
Operator | general aviation : personal |
Make Model Name | Robinson R44 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 25 flight time total : 170 flight time type : 50 |
ASRS Report | 574120 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : far non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Although I've flown in and out of this area many times (approximately 6), this was the first time I needed to file a VFR flight plan due to new ADIZ around the described area. This was also my first flight plan filed and flown for any reason. I was aware and realized I was entering the restricted area, but assumed because of a filed flight plan I would receive instruction on my radio. Not knowing on a VFR plan you fly like a normal VFR flight, contacting towers for instruction or transition in necessary airspace as I'm already used to. Upon contacting baltimore approach I was informed that I had illegally broken restricted airspace and was given phone numbers to contact us customs and baltimore approach. After contacting customs I was questioned for a few moments in person by the secret service and was free to go. I realize, although a learning experience, it was very dangerous to myself and other aircraft possibly in the area and the concern of authorities especially in today's times of high alert securities issues. In closing, I can say this will not happen again and would like to apologize for all inconveniences posed by my actions. The restricted area was aberdeen R-4001A.
Original NASA ASRS Text
Title: R44 HELICOPTER PLT ENTERS THE R-4001A AND THE WASHINGTON DC METROPOLITAN AREA ADIZ WITHOUT AN IFR CLRNC OR DISCRETE TRANSPONDER CODE.
Narrative: ALTHOUGH I'VE FLOWN IN AND OUT OF THIS AREA MANY TIMES (APPROX 6), THIS WAS THE FIRST TIME I NEEDED TO FILE A VFR FLT PLAN DUE TO NEW ADIZ AROUND THE DESCRIBED AREA. THIS WAS ALSO MY FIRST FLT PLAN FILED AND FLOWN FOR ANY REASON. I WAS AWARE AND REALIZED I WAS ENTERING THE RESTRICTED AREA, BUT ASSUMED BECAUSE OF A FILED FLT PLAN I WOULD RECEIVE INSTRUCTION ON MY RADIO. NOT KNOWING ON A VFR PLAN YOU FLY LIKE A NORMAL VFR FLT, CONTACTING TOWERS FOR INSTRUCTION OR TRANSITION IN NECESSARY AIRSPACE AS I'M ALREADY USED TO. UPON CONTACTING BALTIMORE APCH I WAS INFORMED THAT I HAD ILLEGALLY BROKEN RESTRICTED AIRSPACE AND WAS GIVEN PHONE NUMBERS TO CONTACT US CUSTOMS AND BALTIMORE APCH. AFTER CONTACTING CUSTOMS I WAS QUESTIONED FOR A FEW MOMENTS IN PERSON BY THE SECRET SERVICE AND WAS FREE TO GO. I REALIZE, ALTHOUGH A LEARNING EXPERIENCE, IT WAS VERY DANGEROUS TO MYSELF AND OTHER ACFT POSSIBLY IN THE AREA AND THE CONCERN OF AUTHORITIES ESPECIALLY IN TODAY'S TIMES OF HIGH ALERT SECURITIES ISSUES. IN CLOSING, I CAN SAY THIS WILL NOT HAPPEN AGAIN AND WOULD LIKE TO APOLOGIZE FOR ALL INCONVENIENCES POSED BY MY ACTIONS. THE RESTRICTED AREA WAS ABERDEEN R-4001A.
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.