37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 592542 |
Time | |
Date | 200308 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : w29.airport |
State Reference | MD |
Altitude | msl single value : 900 |
Environment | |
Flight Conditions | Mixed |
Weather Elements | Rain Thunderstorm |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon tracon : nhk.tracon |
Operator | general aviation : personal |
Make Model Name | AS 355 Twinstar |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | cruise : level |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : cfi pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 100 flight time total : 10000 flight time type : 20 |
ASRS Report | 592242 |
Person 2 | |
Affiliation | government : military |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
Independent Detector | other controllera |
Resolutory Action | flight crew : exited penetrated airspace |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance FAA Environmental Factor Airspace Structure Aircraft Flight Crew Human Performance |
Primary Problem | FAA |
Air Traffic Incident | Pilot Deviation |
Narrative:
I departed VFR from miller airport (mjx) en route to richmond airport (ric) via chandelle airport (0n4) after checking WX and en route information. While en route and passing over 0n4, I elected, based on current WX conditions and remaining daylight hours, to deviate from my original planned flight routing to hef via 2w5 to avoid the washington prohibited area. While deviating approximately 5-10 mi wsw of 0n4 and flying the aircraft, I reviewed my current washington sectional chart for pertinent information to navigation and communicate into my new destination (hef). I tried to make radio contact with baltimore approach while still en route at 700 ft MSL with no response. I continued to attempt radio contact with other agencies such as local FSS, dover approach 132.425 and patuxent approach 127.95 -- still to no avail. According to a radio call that I believe was intended for my aircraft which I received while monitoring guard frequency 121.5, the controling agency transmitted in the blind that an aircraft squawking 1200 had entered the washington ADIZ approximately 2-3 mi ene of bay bridge airport (W29) which I determined to be my approximately position based on my sectional chart. Once I determined that this was my approximately position, I attempted to make radio contact with guard to identify myself to no avail. I was instructed in the blind by guard to exit the area to the east which I complied with via the shoreline ese due to WX and visibility conditions. I, at this point and location, was able to climb higher in VFR conditions while traveling south to again attempt radio contact with a controling agency to identify myself and obtain clearance. At this point I was able to make radio contact with a controling agency, that I believe was patuxent approach 127.95. I idented myself and obtained a squawk code. They in turn handed me off to potomac approach which handled my aircraft en route to 2w5 where I had to land to wait out WX at my new final destination of hef. While en route to 2w5, potomac approach requested that I call TRACON when I landed at 2w5 on landline. I complied and spoke to a supervisor who informed me that I had entered the washington ADIZ. I explained what I believed to have happened and he then took my pertinent information and informed me that I would be hearing from an FSDO office. Corrective solutions: 1) better communications facilities (rco's) for contacting controling agencies while en route at low flight levels in the vicinity of such restr airspaces to facilitate the en route identify of our aircraft and receive clrncs without having to land and call FSS in the event of a flight plan change for WX or other unforeseen reasons. 2) properly updated aviation sectional navigation charts that depict and explain all the current restr airspaces that have been permanently implemented, ie, washington ADIZ which has been in effect for some time and is not depicted on the current sectional charts. 3) better preflight planning by the PIC if there may be a need to deviate while en route VFR in the areas of sua such as the washington ADIZ. 4) better cooperation and understanding between the homeland security office, transportation safety administration and the FAA on how to develop a system with controls that is designed to promote air commerce both GA and air carrier's.
Original NASA ASRS Text
Title: PLT OF AS55 HELI, UNABLE TO CONTACT ANY CTLING AUTH TO OBTAIN CLRNC, ENTERS DC ADIZ WITHOUT RADIO CONTACT OR DISCRETE SQUAWK. ADVISED IN THE BLIND ON GUARD FREQ TO EXIT.
Narrative: I DEPARTED VFR FROM MILLER ARPT (MJX) ENRTE TO RICHMOND ARPT (RIC) VIA CHANDELLE ARPT (0N4) AFTER CHKING WX AND ENRTE INFO. WHILE ENRTE AND PASSING OVER 0N4, I ELECTED, BASED ON CURRENT WX CONDITIONS AND REMAINING DAYLIGHT HRS, TO DEVIATE FROM MY ORIGINAL PLANNED FLT ROUTING TO HEF VIA 2W5 TO AVOID THE WASHINGTON PROHIBITED AREA. WHILE DEVIATING APPROX 5-10 MI WSW OF 0N4 AND FLYING THE ACFT, I REVIEWED MY CURRENT WASHINGTON SECTIONAL CHART FOR PERTINENT INFO TO NAV AND COMMUNICATE INTO MY NEW DEST (HEF). I TRIED TO MAKE RADIO CONTACT WITH BALTIMORE APCH WHILE STILL ENRTE AT 700 FT MSL WITH NO RESPONSE. I CONTINUED TO ATTEMPT RADIO CONTACT WITH OTHER AGENCIES SUCH AS LCL FSS, DOVER APCH 132.425 AND PATUXENT APCH 127.95 -- STILL TO NO AVAIL. ACCORDING TO A RADIO CALL THAT I BELIEVE WAS INTENDED FOR MY ACFT WHICH I RECEIVED WHILE MONITORING GUARD FREQ 121.5, THE CTLING AGENCY XMITTED IN THE BLIND THAT AN ACFT SQUAWKING 1200 HAD ENTERED THE WASHINGTON ADIZ APPROX 2-3 MI ENE OF BAY BRIDGE ARPT (W29) WHICH I DETERMINED TO BE MY APPROX POS BASED ON MY SECTIONAL CHART. ONCE I DETERMINED THAT THIS WAS MY APPROX POS, I ATTEMPTED TO MAKE RADIO CONTACT WITH GUARD TO IDENT MYSELF TO NO AVAIL. I WAS INSTRUCTED IN THE BLIND BY GUARD TO EXIT THE AREA TO THE E WHICH I COMPLIED WITH VIA THE SHORELINE ESE DUE TO WX AND VISIBILITY CONDITIONS. I, AT THIS POINT AND LOCATION, WAS ABLE TO CLB HIGHER IN VFR CONDITIONS WHILE TRAVELING S TO AGAIN ATTEMPT RADIO CONTACT WITH A CTLING AGENCY TO IDENT MYSELF AND OBTAIN CLRNC. AT THIS POINT I WAS ABLE TO MAKE RADIO CONTACT WITH A CTLING AGENCY, THAT I BELIEVE WAS PATUXENT APCH 127.95. I IDENTED MYSELF AND OBTAINED A SQUAWK CODE. THEY IN TURN HANDED ME OFF TO POTOMAC APCH WHICH HANDLED MY ACFT ENRTE TO 2W5 WHERE I HAD TO LAND TO WAIT OUT WX AT MY NEW FINAL DEST OF HEF. WHILE ENRTE TO 2W5, POTOMAC APCH REQUESTED THAT I CALL TRACON WHEN I LANDED AT 2W5 ON LANDLINE. I COMPLIED AND SPOKE TO A SUPVR WHO INFORMED ME THAT I HAD ENTERED THE WASHINGTON ADIZ. I EXPLAINED WHAT I BELIEVED TO HAVE HAPPENED AND HE THEN TOOK MY PERTINENT INFO AND INFORMED ME THAT I WOULD BE HEARING FROM AN FSDO OFFICE. CORRECTIVE SOLUTIONS: 1) BETTER COMS FACILITIES (RCO'S) FOR CONTACTING CTLING AGENCIES WHILE ENRTE AT LOW FLT LEVELS IN THE VICINITY OF SUCH RESTR AIRSPACES TO FACILITATE THE ENRTE IDENT OF OUR ACFT AND RECEIVE CLRNCS WITHOUT HAVING TO LAND AND CALL FSS IN THE EVENT OF A FLT PLAN CHANGE FOR WX OR OTHER UNFORESEEN REASONS. 2) PROPERLY UPDATED AVIATION SECTIONAL NAV CHARTS THAT DEPICT AND EXPLAIN ALL THE CURRENT RESTR AIRSPACES THAT HAVE BEEN PERMANENTLY IMPLEMENTED, IE, WASHINGTON ADIZ WHICH HAS BEEN IN EFFECT FOR SOME TIME AND IS NOT DEPICTED ON THE CURRENT SECTIONAL CHARTS. 3) BETTER PREFLT PLANNING BY THE PIC IF THERE MAY BE A NEED TO DEVIATE WHILE ENRTE VFR IN THE AREAS OF SUA SUCH AS THE WASHINGTON ADIZ. 4) BETTER COOPERATION AND UNDERSTANDING BTWN THE HOMELAND SECURITY OFFICE, TRANSPORTATION SAFETY ADMINISTRATION AND THE FAA ON HOW TO DEVELOP A SYS WITH CTLS THAT IS DESIGNED TO PROMOTE AIR COMMERCE BOTH GA AND ACR'S.
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.