 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Phl approach controller experienced operational error at 3000 when intrafac coordination failed and conflicting aircraft on approach were not turned soon enough.
| Attributes | |
| ACN | 759004 |
| Time | |
| Date | 200710 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phl.airport |
| State Reference | PA |
| Altitude | msl single value : 3000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : phl.tracon tracon : zspd.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | Dash 8 Series Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer & glide slope : 17 |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument precision |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : phl.tracon |
| Operator | general aviation : personal |
| Make Model Name | Global Express |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | ils localizer only : 6 |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument non precision |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Experience | controller radar : 17 controller time certified in position1 : 9 |
| ASRS Report | 759004 |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | controller : issued alert controller : issued new clearance flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 12000 vertical : 300 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Narrative:
I was working ptw sector when the controller working ard sector told me about 2 back course localizer runway 6 approachs into pne. I told the controller about a DH8A; on a converging ILS runway 17 approach. The DH8A was cleared for the approach and established on the localizer. I noticed the second aircraft for the approach into pne was heading wbound toward the final for runway 17 into phl. The ard controller was busy and I yelled for him to turn his aircraft sbound away from my final. I turn the DH8A wbound; but they got within 3 mi of each other. I think when phl is running approachs to runway 17 pne should not have approachs to runway 6. There is too great a chance for conflict.
Original NASA ASRS Text
Title: PHL APCH CTLR EXPERIENCED OPERROR AT 3000 WHEN INTRAFAC COORD FAILED AND CONFLICTING ACFT ON APCH WERE NOT TURNED SOON ENOUGH.
Narrative: I WAS WORKING PTW SECTOR WHEN THE CTLR WORKING ARD SECTOR TOLD ME ABOUT 2 BACK COURSE LOC RWY 6 APCHS INTO PNE. I TOLD THE CTLR ABOUT A DH8A; ON A CONVERGING ILS RWY 17 APCH. THE DH8A WAS CLRED FOR THE APCH AND ESTABLISHED ON THE LOC. I NOTICED THE SECOND ACFT FOR THE APCH INTO PNE WAS HDG WBOUND TOWARD THE FINAL FOR RWY 17 INTO PHL. THE ARD CTLR WAS BUSY AND I YELLED FOR HIM TO TURN HIS ACFT SBOUND AWAY FROM MY FINAL. I TURN THE DH8A WBOUND; BUT THEY GOT WITHIN 3 MI OF EACH OTHER. I THINK WHEN PHL IS RUNNING APCHS TO RWY 17 PNE SHOULD NOT HAVE APCHS TO RWY 6. THERE IS TOO GREAT A CHANCE FOR CONFLICT.
Data retrieved from NASA's ASRS site as of January 2009 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.