 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Emb-145 flight crew reported they were issued the same altitude going around as the traffic also going around on a crossing runway at phl.
| Attributes | |
| ACN | 1505511 |
| Time | |
| Date | 201712 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PHL.Airport |
| State Reference | PA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Check Pilot |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
I was observing from the jumpseat on a visual approach to runway 27R. The crew was asked by tower to make an south turn to the left to provide more space for crossing traffic landing runway 35 and was cleared to land. While conducting the south turn the aircraft became too high on the glide slope and a go around was executed. The tower told our flight to climb to 2000 ft runway heading. Apparently the traffic landing 35 also executed a go around the same time because they had not received a landing clearance. The tower told the other aircraft to fly runway heading and climb to 2000 ft as well. I did not notice any TA or RA warnings from the TCAS (traffic collision avoidance system).high position on the glideslope during south turn maneuver resulting in a crew initiated go around. In my opinion there should be instructions issued to aircraft on converging visual approaches ahead of time in the event of a go around that will adequately provide separation should both aircraft execute a go around.
Original NASA ASRS Text
Title: EMB-145 flight crew reported they were issued the same altitude going around as the traffic also going around on a crossing runway at PHL.
Narrative: I was observing from the jumpseat on a visual approach to runway 27R. The crew was asked by tower to make an S turn to the left to provide more space for crossing traffic landing runway 35 and was cleared to land. While conducting the S turn the aircraft became too high on the glide slope and a go around was executed. The tower told our flight to climb to 2000 ft runway heading. Apparently the traffic landing 35 also executed a go around the same time because they had not received a landing clearance. The tower told the other aircraft to fly runway heading and climb to 2000 ft as well. I did not notice any TA or RA warnings from the TCAS (Traffic Collision Avoidance System).High position on the glideslope during S turn maneuver resulting in a crew initiated go around. In my opinion there should be instructions issued to aircraft on converging visual approaches ahead of time in the event of a go around that will adequately provide separation should both aircraft execute a go around.
Data retrieved from NASA's ASRS site 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.