 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of a B737-200 made go around after observing a piper seneca on short final on an intersecting runway. Tower controller instruction the seneca to go around.
| Attributes | |
| ACN | 429567 |
| Time | |
| Date | 199902 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phl.airport |
| Altitude | agl single value : 50 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : phl.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach landing : go around |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : phl.tower |
| Make Model Name | PA-34-200 Seneca I |
| Flight Phase | descent : approach landing : go around |
| Route In Use | approach : visual |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : multi engine pilot : flight engineer |
| Experience | fss specialist : 200 flight time total : 15000 flight time type : 4000 |
| ASRS Report | 429567 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : commercial |
| Events | |
| Anomaly | conflict : airborne less severe |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance flight crew : executed go around |
| Miss Distance | horizontal : 2000 vertical : 30 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure |
Narrative:
We had been cleared to land by tower on runway 27R. Unknown to us (not advised), a seneca was on final for intersecting runway 35. After crossing the threshold and starting to retard power to flare, we saw a seneca about to cross the threshold for runway 35 landing. At that time tower issued go around instructions to seneca and told us to land. By that time we had already initiated go around. We were resequenced for normal landing, filed near miss report with phl next day, and filed ASR with company. Factors: was told on phone that controller training was in progress at time. Was not advised by tower of traffic on final for runway 35. Go around/land instructions given much too late to avoid conflict. Speeds were such that had no action been taken the seneca would have been through intersection 3-5 seconds prior to us. Go around was straight ahead.
Original NASA ASRS Text
Title: FLC OF A B737-200 MADE GAR AFTER OBSERVING A PIPER SENECA ON SHORT FINAL ON AN INTERSECTING RWY. TWR CTLR INSTRUCTION THE SENECA TO GO AROUND.
Narrative: WE HAD BEEN CLRED TO LAND BY TWR ON RWY 27R. UNKNOWN TO US (NOT ADVISED), A SENECA WAS ON FINAL FOR INTERSECTING RWY 35. AFTER XING THE THRESHOLD AND STARTING TO RETARD PWR TO FLARE, WE SAW A SENECA ABOUT TO CROSS THE THRESHOLD FOR RWY 35 LNDG. AT THAT TIME TWR ISSUED GAR INSTRUCTIONS TO SENECA AND TOLD US TO LAND. BY THAT TIME WE HAD ALREADY INITIATED GAR. WE WERE RESEQUENCED FOR NORMAL LNDG, FILED NEAR MISS RPT WITH PHL NEXT DAY, AND FILED ASR WITH COMPANY. FACTORS: WAS TOLD ON PHONE THAT CTLR TRAINING WAS IN PROGRESS AT TIME. WAS NOT ADVISED BY TWR OF TFC ON FINAL FOR RWY 35. GAR/LAND INSTRUCTIONS GIVEN MUCH TOO LATE TO AVOID CONFLICT. SPDS WERE SUCH THAT HAD NO ACTION BEEN TAKEN THE SENECA WOULD HAVE BEEN THROUGH INTXN 3-5 SECONDS PRIOR TO US. GAR WAS STRAIGHT AHEAD.
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.