 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mia TRACON departure controller reports of being inundated with traffic and stopping departures at least three times to get sector under control. Controller has an operational error with an aircraft they turned away from another departure; but this aircraft then became a conflict with an arrival on the downwind. Controller reported the front line manager in tower instructed the local controller to disregard the flow and launch harder because OJT was being performed in the departure sector.
| Attributes | |
| ACN | 1311281 |
| Time | |
| Date | 201511 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | MIA.TRACON |
| State Reference | FL |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Saab 340 Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Instructor Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 29 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
Working the south departure position while providing OJT (on job training) with frontal passage weather impacting all departures routed to the east of mia. Traffic volume was at maximum capacity. During the session I had to stop departures twice to minimize my volume. The supervisor stopped departures one more additional time in order to minimize traffic. During a period of high traffic my developmental turned aircraft X to a 90 degree heading in order to avoid a conflict simultaneously the tower departed aircraft Z that did not tag up because of a wrong squawk code while attempting to correct the squawk code issue aircraft X continued to travel easterly and came in conflict with aircraft Y on downwind to mia. Both aircraft were at 6000 feet. No ca/MSAW alert sounded. I continued to work the position for a period of time because of a staffing shortage.traffic was extreme and ZMA had in trail restrictions.after stopping departures and restarting them I asked the tower for additional in trail and the tower supervisor instructed the local controller to depart aircraft faster. The tower controller told the supervisor that ZMA had flow restrictions but the tower supervisor told him to disregard the restrictions and launch harder because OJT was being performed on the departure procedure. All of this information was brought to management's attention and both the tower supervisor and tower controller were interviewed.in my opinion all the parts of this puzzle; weather reroutes; heightened arrivals to tmb due to nascar activity; skydive operations; etc were not taken into consideration with regards to the position I was working causing an overload of traffic.
Original NASA ASRS Text
Title: MIA TRACON Departure Controller reports of being inundated with traffic and stopping departures at least three times to get sector under control. Controller has an operational error with an aircraft they turned away from another departure; but this aircraft then became a conflict with an arrival on the downwind. Controller reported the Front Line Manager in Tower instructed the Local Controller to disregard the flow and launch harder because OJT was being performed in the departure sector.
Narrative: Working the south departure position while providing OJT (On Job Training) with frontal passage weather impacting all departures routed to the east of MIA. Traffic volume was at maximum capacity. During the session I had to stop departures twice to minimize my volume. The supervisor stopped departures one more additional time in order to minimize traffic. During a period of high traffic my developmental turned Aircraft X to a 90 degree heading in order to avoid a conflict simultaneously the tower departed Aircraft Z that did not tag up because of a wrong squawk code while attempting to correct the squawk code issue Aircraft X continued to travel easterly and came in conflict with Aircraft Y on downwind to MIA. Both aircraft were at 6000 feet. No CA/MSAW alert sounded. I continued to work the position for a period of time because of a staffing shortage.Traffic was extreme and ZMA had in trail restrictions.After stopping departures and restarting them I asked the tower for additional in trail and the tower supervisor instructed the local controller to depart aircraft faster. The tower controller told the supervisor that ZMA had flow restrictions but the tower supervisor told him to disregard the restrictions and launch harder because OJT was being performed on the departure procedure. All of this information was brought to management's attention and both the tower supervisor and tower controller were interviewed.In my opinion all the parts of this puzzle; weather reroutes; heightened arrivals to TMB due to NASCAR activity; skydive operations; etc were not taken into consideration with regards to the position I was working causing an overload of traffic.
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.