37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1428076 |
Time | |
Date | 201703 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Aircraft 1 | |
Make Model Name | Caravan Undifferentiated |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Flight Phase | Takeoff |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was the front line manager (flm) in the area. We were in the middle of the [afternoon] arrival bank after a thunderstorm and cold front moved through. The winds at ZZZ were 210@18g33kt. The winds aloft at 2000' were 230@40KT. My coordinator came to me around XA05 and explained that the controller was concerned that ZZZ tower launched successive aircraft on the same heading. The problem being that the lead aircraft was aircraft X and the successive departure was aircraft Y. I looked at the radar and there was adequate separation but I reviewed the dalr [digital audio legal recorder] to double check. I was able to listen to local controller (local) at ZZZ tower. He cleared aircraft X for takeoff of runway xy and assigned runway heading. A moment later he told aircraft Y to line up and wait (luaw) on runway xy. A few moments later local cleared aircraft Y for take-off runway xy on a heading of 320. Because of the strong winds out of the southwest; aircraft X was well right of the runway xy centerline. When aircraft Y got airborne and checked in; it looked like both aircraft were on 320 headings. The controller turned aircraft X left to a 270 heading to avoid the targets merging and then told the coordinator. I understand that ZZZ tower complied with the 7110.65 in this incident. But this is not the first time that I have been told by my controllers of unsafe situations concerning aircraft types and tower assigned headings similar to this. I would like this report to make all controllers aware of this potential unsafe situation. It is my goal for local controllers to be aware of winds and the effects on small aircraft. I would also like ZZZ tower to know that they can call and appreq different headings for situations like this. I know it probably looked worse on our radar than it did out the window of the tower; but I feel this is an unsafe practice. We are restricted from the letter of agreement (LOA) not being able to turn aircraft until out of 3000' and are sometimes handed aircraft on poor headings for our sequencing. Even though ZZZ tower can assign those headings; we the departure controllers are stuck having to deal with consequences sometimes.
Original NASA ASRS Text
Title: Front Line Manager reported that there were high winds causing drift of aircraft on departure. This lead to an unsafe situation when the faster aircraft departed behind the slower aircraft.
Narrative: I was the Front Line Manager (FLM) in the area. We were in the middle of the [afternoon] arrival bank after a thunderstorm and cold front moved through. The winds at ZZZ were 210@18G33KT. The winds aloft at 2000' were 230@40KT. My coordinator came to me around XA05 and explained that the controller was concerned that ZZZ tower launched successive aircraft on the same heading. The problem being that the lead aircraft was Aircraft X and the successive departure was Aircraft Y. I looked at the radar and there was adequate separation but I reviewed the DALR [Digital Audio Legal Recorder] to double check. I was able to listen to Local Controller (LCL) at ZZZ tower. He cleared Aircraft X for takeoff of Runway XY and assigned runway heading. A moment later he told Aircraft Y to Line up and Wait (LUAW) on Runway XY. A few moments later LCL cleared Aircraft Y for take-off Runway XY on a heading of 320. Because of the strong winds out of the Southwest; Aircraft X was well right of the Runway XY centerline. When Aircraft Y got airborne and checked in; it looked like both aircraft were on 320 headings. The controller turned Aircraft X left to a 270 heading to avoid the targets merging and then told the coordinator. I understand that ZZZ tower complied with the 7110.65 in this incident. But this is not the first time that I have been told by my controllers of unsafe situations concerning aircraft types and tower assigned headings similar to this. I would like this report to make all controllers aware of this potential unsafe situation. It is my goal for Local Controllers to be aware of winds and the effects on small aircraft. I would also like ZZZ tower to know that they can call and APPREQ different headings for situations like this. I know it probably looked worse on our radar than it did out the window of the tower; but I feel this is an unsafe practice. We are restricted from the Letter of Agreement (LOA) not being able to turn aircraft until out of 3000' and are sometimes handed aircraft on poor headings for our sequencing. Even though ZZZ tower can assign those headings; we the departure controllers are stuck having to deal with consequences sometimes.
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.