37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1533826 |
Time | |
Date | 201804 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PHL.Tower |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation V/Ultra/Encore (C560) |
Operating Under FAR Part | Part 91 |
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 | Pilot Flying Single Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 75 Flight Crew Total 5400 Flight Crew Type 600 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Miss Distance | Vertical 500 |
Narrative:
Upon being cleared for a visual approach at runway 35 aircraft Y was instructed to slow for the intersecting runway 27R on which they were doing an approach as well. Aircraft Y did not respond. About 30 seconds passed and tower asked if aircraft Y copied their instructions to slow. They then responded that they had missed that instruction. ATC then said something to the affect that it is 'too late anyway'. Tower then instructed me to go around; fly heading 350 and maintain runway heading. Before I could reply; and after I had started my go around procedure; aircraft Y responded 'go around; fly heading 350; maintain 3;000 feet'. Right away I saw aircraft Y climbing and turning north while I was climbing on heading 350. I leveled off at 800 feet as they passed overhead. Tower then instructed me to level off. I am not sure if aircraft Y ever had me in sight.I feel that the problem was caused by two reasons; first aircraft Y's lack of situational awareness and communication initially; and second; a short radio blockage caused possibly by another aircraft; which resulted in aircraft Y thinking they were the ones instructed to go-around.
Original NASA ASRS Text
Title: Corporate pilot reported an airborne conflict during a go-around after another aircraft mistakenly followed their go-around instruction.
Narrative: Upon being cleared for a Visual Approach at runway 35 Aircraft Y was instructed to slow for the intersecting runway 27R on which they were doing an approach as well. Aircraft Y did not respond. About 30 seconds passed and Tower asked if Aircraft Y copied their instructions to slow. They then responded that they had missed that instruction. ATC then said something to the affect that it is 'too late anyway'. Tower then instructed me to go around; fly heading 350 and maintain runway heading. Before I could reply; and after I had started my go around procedure; Aircraft Y responded 'Go around; fly heading 350; maintain 3;000 feet'. Right away I saw Aircraft Y climbing and turning north while I was climbing on heading 350. I leveled off at 800 feet as they passed overhead. Tower then instructed me to level off. I am not sure if Aircraft Y ever had me in sight.I feel that the problem was caused by two reasons; first Aircraft Y's lack of situational awareness and communication initially; and second; a short radio blockage caused possibly by another aircraft; which resulted in Aircraft Y thinking they were the ones instructed to 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.