![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 541969 |
Time | |
Date | 200203 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : phl.airport |
State Reference | PA |
Altitude | agl single value : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : phl.tower |
Operator | common carrier : air carrier |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 27r other |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : phl.tower |
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 : 35 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : cfi pilot : atp |
Experience | flight time last 90 days : 30 flight time total : 12000 flight time type : 600 |
ASRS Report | 541969 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne critical non adherence : published procedure other anomaly other |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | controller : separated traffic flight crew : executed go around flight crew : took evasive action |
Miss Distance | horizontal : 5000 vertical : 500 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
Inside the OM on a visual approach to runway 27R at phl, ATC asked us to do an s-turn for traffic landing on runway 35. We did the s-turn and when we turned back towards the runway and saw the traffic (a dash 8) on final for runway 35, realized he was not going to land and clear our runway before we landed, we decided to go around but at the same time the tower told the dash 8 to go around. We had to maneuver at a low altitude and became slightly unstabilized but felt it was safer to land than go around because of the dash 8 go around which put him in our flight path if we had gone around. On our first approach, we were kept high on downwind and then cleared for a visual approach. On final, we were still a little high and fast so we performed a go around. Also, while taxiing in, we saw another aircraft go around. The WX was good, but phl seemed to be having trouble managing the high volume of traffic.
Original NASA ASRS Text
Title: A321 TOOK EVASIVE ACTION BY LNDG RATHER THAN GOING AROUND DUE TO THE PROJECTED FLT PATH OF A DEHAVILLAND DASH 8 ON FINAL FOR ANOTHER INTERSECTING RWY. HOWEVER, THE TWR, AT THAT SAME TIME, SENT THE DASH 8 AROUND WHICH WOULD HAVE CAUSED THE 2 ACFT'S FLT PATHS TO INTERSECT IF THE A321 WOULD HAVE ALSO GONE AROUND.
Narrative: INSIDE THE OM ON A VISUAL APCH TO RWY 27R AT PHL, ATC ASKED US TO DO AN S-TURN FOR TFC LNDG ON RWY 35. WE DID THE S-TURN AND WHEN WE TURNED BACK TOWARDS THE RWY AND SAW THE TFC (A DASH 8) ON FINAL FOR RWY 35, REALIZED HE WAS NOT GOING TO LAND AND CLR OUR RWY BEFORE WE LANDED, WE DECIDED TO GO AROUND BUT AT THE SAME TIME THE TWR TOLD THE DASH 8 TO GO AROUND. WE HAD TO MANEUVER AT A LOW ALT AND BECAME SLIGHTLY UNSTABILIZED BUT FELT IT WAS SAFER TO LAND THAN GO AROUND BECAUSE OF THE DASH 8 GAR WHICH PUT HIM IN OUR FLT PATH IF WE HAD GONE AROUND. ON OUR FIRST APCH, WE WERE KEPT HIGH ON DOWNWIND AND THEN CLRED FOR A VISUAL APCH. ON FINAL, WE WERE STILL A LITTLE HIGH AND FAST SO WE PERFORMED A GAR. ALSO, WHILE TAXIING IN, WE SAW ANOTHER ACFT GO AROUND. THE WX WAS GOOD, BUT PHL SEEMED TO BE HAVING TROUBLE MANAGING THE HIGH VOLUME OF TFC.
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.