 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Dc ADIZ penetrated by a PA31-350 pilot during a GA VFR, no flight plan, flight 10 ssw of baltimore, md.
| Attributes | |
| ACN | 587243 |
| Time | |
| Date | 200207 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | navaid : bal.vortac |
| State Reference | MD |
| Altitude | msl single value : 10500 |
| Environment | |
| Flight Conditions | VMC |
| Weather Elements | Thunderstorm Turbulence |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | general aviation : personal |
| Make Model Name | PA-31 Navajo Chieftan/Mojave/Navajo T1020 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Flight Plan | None |
| Aircraft 2 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | other |
| Make Model Name | Fighter |
| Operating Under FAR Part | Part 91 |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : multi engine pilot : cfi pilot : commercial pilot : instrument |
| Experience | flight time last 90 days : 110 flight time total : 2150 flight time type : 900 |
| ASRS Report | 587243 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach controller : departure |
| Events | |
| Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
| Independent Detector | atc equipment other atc equipment : radar other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory flight crew : exited penetrated airspace other |
| Consequence | faa : reviewed incident with flight crew faa : investigated |
| Supplementary | |
| Problem Areas | ATC Human Performance Flight Crew Human Performance Environmental Factor Airspace Structure |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
The event occurred when I departed allentown VFR at 10500 ft, proceeding direct to hilton head, south carolina. I departed getting radar advisories with philadelphia approach during my climb and cruise until I reached baltimore's airspace. Philadelphia approach could not give me the handoff, so I squawked 1200 and tried to get in touch with pct approach. At this point, IM 35 mi north of balance at 10500 ft on a heading of 200 degrees. They said they were busy and were unable to give me flight following and to try them later in a few mins. So, I proceeded over their airspace for a few mins and tried to contact them again. At this point, 5 mi south of baltimore, I asked for another frequency for advisories. There was a lot of frequency congestion and after a few mins had passed, he then comes back with a squawk code to help find my location and help me get advisories. By the time he gets back to me, he tells me I have entered the washington ADIZ restr airspace and to divert to a heading of 100 degrees. I did so immediately and was then escorted by 2 fighter jets while en route. They determined I was no risk and let me continue sbound once I was clear. The incident did require me to get a hold of the operations manager at potomac. The circumstances that caused the incident were frequency congestion, turbulence, no warnings from any radar facilities or FSS, and the fact that I was tired. I was told by potomac they have had 300 incidents, at least, in the washington area alone. I have a clean record and always abide by the rules.
Original NASA ASRS Text
Title: DC ADIZ PENETRATED BY A PA31-350 PLT DURING A GA VFR, NO FLT PLAN, FLT 10 SSW OF BALTIMORE, MD.
Narrative: THE EVENT OCCURRED WHEN I DEPARTED ALLENTOWN VFR AT 10500 FT, PROCEEDING DIRECT TO HILTON HEAD, SOUTH CAROLINA. I DEPARTED GETTING RADAR ADVISORIES WITH PHILADELPHIA APCH DURING MY CLB AND CRUISE UNTIL I REACHED BALTIMORE'S AIRSPACE. PHILADELPHIA APCH COULD NOT GIVE ME THE HDOF, SO I SQUAWKED 1200 AND TRIED TO GET IN TOUCH WITH PCT APCH. AT THIS POINT, IM 35 MI N OF BAL AT 10500 FT ON A HDG OF 200 DEGS. THEY SAID THEY WERE BUSY AND WERE UNABLE TO GIVE ME FLT FOLLOWING AND TO TRY THEM LATER IN A FEW MINS. SO, I PROCEEDED OVER THEIR AIRSPACE FOR A FEW MINS AND TRIED TO CONTACT THEM AGAIN. AT THIS POINT, 5 MI S OF BALTIMORE, I ASKED FOR ANOTHER FREQ FOR ADVISORIES. THERE WAS A LOT OF FREQ CONGESTION AND AFTER A FEW MINS HAD PASSED, HE THEN COMES BACK WITH A SQUAWK CODE TO HELP FIND MY LOCATION AND HELP ME GET ADVISORIES. BY THE TIME HE GETS BACK TO ME, HE TELLS ME I HAVE ENTERED THE WASHINGTON ADIZ RESTR AIRSPACE AND TO DIVERT TO A HDG OF 100 DEGS. I DID SO IMMEDIATELY AND WAS THEN ESCORTED BY 2 FIGHTER JETS WHILE ENRTE. THEY DETERMINED I WAS NO RISK AND LET ME CONTINUE SBOUND ONCE I WAS CLR. THE INCIDENT DID REQUIRE ME TO GET A HOLD OF THE OPS MGR AT POTOMAC. THE CIRCUMSTANCES THAT CAUSED THE INCIDENT WERE FREQ CONGESTION, TURB, NO WARNINGS FROM ANY RADAR FACILITIES OR FSS, AND THE FACT THAT I WAS TIRED. I WAS TOLD BY POTOMAC THEY HAVE HAD 300 INCIDENTS, AT LEAST, IN THE WASHINGTON AREA ALONE. I HAVE A CLEAN RECORD AND ALWAYS ABIDE BY THE RULES.
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.