37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1244503 |
Time | |
Date | 201503 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | MCO.Airport |
State Reference | FL |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach Landing |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.5 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Suspected loss of wake turbulence separation between aircraft X and aircraft Y on final runway 36L. Aircraft X had been cleared to land and aircraft Y was in trail with spacing deteriorating. When the spacing was approaching minimums; final (1g) called the tower on the override line advising if aircraft Y does not have aircraft X in sight to break him out. I then attempted to contact aircraft Y twice but received no response. After the second attempt; the compression was below the minimum separation required for wake turbulence separation. By the time aircraft y checked on; aircraft X was cross the landing threshold and rolling out. Aircraft Y reported he had aircraft X on roll out in sight. I issued him a cautionary and cleared him to land. Aircraft Y landed without further incident.make sure the aircraft is in communication with either tower or final when you are about to lose separation on final; or cancel the approach clearance in enough time so it's not an issue during transfer of communication.
Original NASA ASRS Text
Title: An MCO Controller reports of a loss of separation between two aircraft on final. The Controller tried to break out the second aircraft but it was not on frequency until the loss had happened. The second aircraft landed.
Narrative: Suspected loss of wake turbulence separation between aircraft X and aircraft Y on final runway 36L. Aircraft X had been cleared to land and aircraft Y was in trail with spacing deteriorating. When the spacing was approaching minimums; final (1g) called the tower on the override line advising if aircraft Y does not have aircraft X in sight to break him out. I then attempted to contact aircraft Y twice but received no response. After the second attempt; the compression was below the minimum separation required for wake turbulence separation. By the time aircraft y checked on; aircraft X was cross the landing threshold and rolling out. Aircraft Y reported he had aircraft X on roll out in sight. I issued him a cautionary and cleared him to land. Aircraft Y landed without further incident.Make sure the aircraft is in communication with either tower or final when you are about to lose separation on final; or cancel the approach clearance in enough time so it's not an issue during transfer of communication.
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.