37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1439974 |
Time | |
Date | 201704 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | P31.TRACON |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Bell Helicopter Textron Undifferentiated or Other Model |
Flight Phase | Final Approach |
Flight Plan | VFR |
Person 1 | |
Function | Approach |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
I relieved a trainer and trainee but was unsure of how their plan would work with a 100 knot overtake and 5 miles closing to 3 between an MD80 and a bell helicopter. I was asking questions expecting a post overlap briefing but the trainer left the position. Tower called to ask if they needed to turn out the helo on a practice approach in VFR conditions was being overtaken by 100 knots and I said yes turn him out now. Tower waited for a mile or so because they had traffic in their pattern. The helo finally turned out on what appeared to be a 010 heading instead of a 080 heading as he was assigned. I think the wind was a factor. He appeared to be head on with the MD80 and I asked the helo to level off at 800 feet which is below the MVA of 1700 feet. I did this to avoid a collision with the MD80 and the helo. I am filing this report because I felt by asking the helo to level off at 800 feet for a couple seconds in his departure climb that it would avoid a collision with an MD80. I don't understand why the FAA no longer requires an overlap from a controller giving another controller a briefing to assume the position they have been working. I also will not take on a situation with an impending separation error again and instead let the controller work out their plan whatever that is; then assume the position after all separation errors have been resolved.bring back the post 2 minute briefing and don't expect controllers to immediately assume a position just because it's time for the current controllers break. 5 minutes can make a huge difference in an imminent situation that the current controller is much more familiar with as well as has already executed whatever plan was in their mind.
Original NASA ASRS Text
Title: P31 TRACON Controller reported an unsafe situation where a jet overtook a helicopter on final.
Narrative: I relieved a trainer and trainee but was unsure of how their plan would work with a 100 knot overtake and 5 miles closing to 3 between an MD80 and a Bell Helicopter. I was asking questions expecting a post overlap briefing but the trainer left the position. Tower called to ask if they needed to turn out the helo on a practice approach in VFR conditions was being overtaken by 100 knots and I said yes turn him out now. Tower waited for a mile or so because they had traffic in their pattern. The helo finally turned out on what appeared to be a 010 heading instead of a 080 heading as he was assigned. I think the wind was a factor. He appeared to be head on with the MD80 and I asked the helo to level off at 800 feet which is below the MVA of 1700 feet. I did this to avoid a collision with the MD80 and the helo. I am filing this report because I felt by asking the helo to level off at 800 feet for a couple seconds in his departure climb that it would avoid a collision with an MD80. I don't understand why the FAA no longer requires an overlap from a controller giving another controller a briefing to assume the position they have been working. I also will not take on a situation with an impending separation error again and instead let the controller work out their plan whatever that is; then assume the position after all separation errors have been resolved.Bring back the post 2 minute briefing and don't expect controllers to immediately assume a position just because it's time for the current controllers break. 5 minutes can make a huge difference in an imminent situation that the current controller is much more familiar with as well as has already executed whatever plan was in their mind.
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.