37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1743967 |
Time | |
Date | 202005 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | F11.TRACON |
State Reference | FL |
Environment | |
Flight Conditions | Marginal |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict NMAC |
Narrative:
On transition from center to mco approach; we were given a clearance to cross bairn int at FL110 on the BAIRN4 arrival. We had just switched to mco approach while we were leveling at the assigned fix at the assigned altitude. As soon as we checked in; mco approach alerts us to VFR traffic at twelve o'clock and four miles at FL105 and to climb and maintain FL120. In the seconds between the notification and execution of the order; I simultaneously scanned the nd and peered out the windscreen to visualize traffic while reaching to dial in the newly assigned altitude. As I pulled FL120 to command open climb; we got the RA to climb. We performed the memory items and executed. The last I saw the red traffic indicated by TCAS; it was 400 ft. Below us. There is no reason this should have occurred. Mia and mco controllers should have coordinated and issued an altered clearance well ahead of time to prevent the close incursion. This aircraft didn't just appear at the altitude; he was mode C equipped and the whole situation could have been prevented had the controllers done their jobs. Instead; and aircraft carrying approximately 140 souls onboard was forced to perform an evasive maneuver to avoid collision. Suggestions: ATC needs to pay attention 100% of the time and anticipate where aircraft are and where aircraft will soon be. I'm actually at a loss as to prevention. ATC is usually very good; especially mia and mco. But one moment of distraction by a controller can be catastrophic.
Original NASA ASRS Text
Title: A320 Captain reported an NMAC event under ATC control during arrival.
Narrative: On transition from Center to MCO approach; we were given a clearance to cross BAIRN int at FL110 on the BAIRN4 arrival. We had just switched to MCO approach while we were leveling at the assigned fix at the assigned altitude. As soon as we checked in; MCO approach alerts us to VFR traffic at twelve o'clock and four miles at FL105 and to climb and maintain FL120. In the seconds between the notification and execution of the order; I simultaneously scanned the ND and peered out the windscreen to visualize traffic while reaching to dial in the newly assigned altitude. As I pulled FL120 to command Open Climb; we got the RA to climb. We performed the memory items and executed. The last I saw the red traffic indicated by TCAS; it was 400 ft. below us. There is no reason this should have occurred. MIA and MCO controllers should have coordinated and issued an altered clearance well ahead of time to prevent the close incursion. This aircraft didn't just appear at the altitude; he was mode C equipped and the whole situation could have been prevented had the controllers done their jobs. Instead; and aircraft carrying approximately 140 souls onboard was forced to perform an evasive maneuver to avoid collision. Suggestions: ATC needs to pay attention 100% of the time and anticipate where aircraft are and where aircraft will soon be. I'm actually at a loss as to prevention. ATC is usually very good; especially MIA and MCO. But one moment of distraction by a controller can be catastrophic.
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.