![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 598869 |
| Time | |
| Date | 200311 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | special use airspace : dcadiz.othersua |
| State Reference | DC |
| Altitude | msl single value : 2000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | general aviation : personal |
| Make Model Name | PA-34-200 Seneca I |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | other |
| Flight Phase | descent : approach |
| Route In Use | approach : traffic pattern arrival : vfr |
| Flight Plan | None |
| Aircraft 2 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | other |
| Make Model Name | Military |
| Flight Phase | cruise : level |
| Route In Use | enroute : direct |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 88.3 flight time total : 5900 flight time type : 2500 |
| ASRS Report | 598869 |
| Person 2 | |
| Function | observation : observer |
| 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 : investigated faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Airspace Structure |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I departed south jersey airport on a logistic flight to ecg with a stop in manassas, va. I was not able to talk to acy approach due to heavy traffic and decided to continue VFR at a low altitude because of class B airspace. I had purchased a new washington sectional at south jersey so that I could stay clear of the washington ADIZ area. I spent most of my navigating time with low en route charts and misread what I thought was restr. I was monitoring 121.5 and attempted to communicate with the intercepting aircraft, but got no answer. I was flying with the aid of a GPS and had no intention of violating the washington ADIZ. I will file IFR for any flight within 100 mi of washington, rain or shine, from now on! My copilot and I have learned a lot from this experience. We both misread the chart.
Original NASA ASRS Text
Title: A PA34 PLT VIOLATED THE DC ADIZ.
Narrative: I DEPARTED SOUTH JERSEY ARPT ON A LOGISTIC FLT TO ECG WITH A STOP IN MANASSAS, VA. I WAS NOT ABLE TO TALK TO ACY APCH DUE TO HVY TFC AND DECIDED TO CONTINUE VFR AT A LOW ALT BECAUSE OF CLASS B AIRSPACE. I HAD PURCHASED A NEW WASHINGTON SECTIONAL AT SOUTH JERSEY SO THAT I COULD STAY CLR OF THE WASHINGTON ADIZ AREA. I SPENT MOST OF MY NAVING TIME WITH LOW ENRTE CHARTS AND MISREAD WHAT I THOUGHT WAS RESTR. I WAS MONITORING 121.5 AND ATTEMPTED TO COMMUNICATE WITH THE INTERCEPTING ACFT, BUT GOT NO ANSWER. I WAS FLYING WITH THE AID OF A GPS AND HAD NO INTENTION OF VIOLATING THE WASHINGTON ADIZ. I WILL FILE IFR FOR ANY FLT WITHIN 100 MI OF WASHINGTON, RAIN OR SHINE, FROM NOW ON! MY COPLT AND I HAVE LEARNED A LOT FROM THIS EXPERIENCE. WE BOTH MISREAD THE CHART.
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.