 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot reports of an RA caused by an aircraft going mach 1 that went through its assigned altitude.
| Attributes | |
| ACN | 1195191 |
| Time | |
| Date | 201408 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | OAKX.ARTCC |
| State Reference | FO |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 4 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
On descent into oakb we were assigned a speed close to minimum clean speed and given a vector for 'traffic and approach.' during descent to fl 240 as cleared; first officer responded crisply and smoothly to a climb RA (I reported it to ATC) the controller said it was an aircraft doing mach 1. Closest vertical separation to traffic was 700 feet. We were clear of conflict by FL250 and told to then maintain FL250. The subsequent vectors; approach; and landing were normal.the controller alluded to the fact that at mach 1 the aircraft had ballooned above his cleared altitude on level off. We could neither see the traffic nor hear him on our VHF assigned frequency. I acknowledge that traffic separation in a combat area must be challenging at best. The controller seemed to handle the conflict smoothly and professionally. If further lateral separation than currently used is possible; it might mitigate some of these traffic conflicts. What a great tool TCAS is!
Original NASA ASRS Text
Title: Pilot reports of an RA caused by an aircraft going Mach 1 that went through its assigned altitude.
Narrative: On descent into OAKB we were assigned a speed close to minimum clean speed and given a vector for 'Traffic and approach.' During descent to FL 240 as cleared; First Officer responded crisply and smoothly to a climb RA (I reported it to ATC) the Controller said it was an aircraft doing Mach 1. Closest vertical separation to traffic was 700 feet. We were clear of conflict by FL250 and told to then maintain FL250. The subsequent vectors; approach; and landing were normal.The Controller alluded to the fact that at Mach 1 the aircraft had ballooned above his cleared altitude on level off. We could neither see the traffic nor hear him on our VHF assigned frequency. I acknowledge that traffic separation in a combat area must be challenging at best. The Controller seemed to handle the conflict smoothly and professionally. If further lateral separation than currently used is possible; it might mitigate some of these traffic conflicts. What a great tool TCAS is!
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.