 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
PA23 pilot departed opf. Overflew mia, fll, and fex. Due to frequency congestion was unable to contact fex prior to entering their airspace.
| Attributes | |
| ACN | 402020 |
| Time | |
| Date | 199805 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : fex airport : fll |
| State Reference | FL |
| Altitude | msl bound lower : 2500 msl bound upper : 2500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : fex |
| Operator | general aviation : personal |
| Make Model Name | PA-23 Apache (& Geronimo Apache) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Flight Plan | None |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 19000 flight time type : 400 |
| ASRS Report | 402020 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : exited adverse environment |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
| Situations | |
| ATC Facility | procedure or policy : unspecified |
Narrative:
Departed opf at XA35. Immediately contacted mia approach for advisories. Mia, a few mins later, turned us over to fll tower. Mia had assigned us altitude 2500 ft. Fll tower instructed us to pass over the field at 2500 ft. After passing over fll airport, fll tower told us to contact fex tower. At this point we were already either in or skirting fex class D airspace. We made 6 attempts to contact fex, but due to radio frequency congestion, were unable to do so. During our attempts, I headed directly offshore to avoid fex airspace. Unable to contact fex, we contacted pmp airport tower (our destination). They cleared us for approach runway 23. Once on the ground, we told pmp ground about the experience. They said it was nothing new, it happens all the time due to the close proximity of the 4 airports involved. There should be a single frequency and controller (corridor controller) for traffic (VFR) in this area.
Original NASA ASRS Text
Title: PA23 PLT DEPARTED OPF. OVERFLEW MIA, FLL, AND FEX. DUE TO FREQ CONGESTION WAS UNABLE TO CONTACT FEX PRIOR TO ENTERING THEIR AIRSPACE.
Narrative: DEPARTED OPF AT XA35. IMMEDIATELY CONTACTED MIA APCH FOR ADVISORIES. MIA, A FEW MINS LATER, TURNED US OVER TO FLL TWR. MIA HAD ASSIGNED US ALT 2500 FT. FLL TWR INSTRUCTED US TO PASS OVER THE FIELD AT 2500 FT. AFTER PASSING OVER FLL ARPT, FLL TWR TOLD US TO CONTACT FEX TWR. AT THIS POINT WE WERE ALREADY EITHER IN OR SKIRTING FEX CLASS D AIRSPACE. WE MADE 6 ATTEMPTS TO CONTACT FEX, BUT DUE TO RADIO FREQ CONGESTION, WERE UNABLE TO DO SO. DURING OUR ATTEMPTS, I HEADED DIRECTLY OFFSHORE TO AVOID FEX AIRSPACE. UNABLE TO CONTACT FEX, WE CONTACTED PMP ARPT TWR (OUR DEST). THEY CLRED US FOR APCH RWY 23. ONCE ON THE GND, WE TOLD PMP GND ABOUT THE EXPERIENCE. THEY SAID IT WAS NOTHING NEW, IT HAPPENS ALL THE TIME DUE TO THE CLOSE PROX OF THE 4 ARPTS INVOLVED. THERE SHOULD BE A SINGLE FREQ AND CTLR (CORRIDOR CTLR) FOR TFC (VFR) IN THIS AREA.
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.