![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1318867 |
| Time | |
| Date | 201512 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5.0 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
We were on noise abatement procedures for midnight operations off ZZZ and ZZZ1. I told ZZZ to hold their night departures because they instantly conflict with ZZZ1 departures. Then I gave ZZZ1 a departure release. About 4 minutes go by and I see a target climbing off of ZZZ. I get a call from ZZZ apologizing for launching an aircraft. On initial contact I turn the ZZZ departure east to a 050 heading because my ZZZ1 departure is climbing fast. If I had not gotten communication when I did they could have potentially hit. As it was I believe standard separation was still lost between the two departures. ZZZ failed to follow a control instruction resulting in an unsafe situation.the noise abatement departure off ZZZ and ZZZ1 are designed in a way that they automatically conflict. I would not be surprised if there is a long history of conflicts like this.
Original NASA ASRS Text
Title: The Tower Controller was supposed to hold a departure but allowed the aircraft to depart. The aircraft was in conflict with a departure from an adjacent airport.
Narrative: We were on noise abatement procedures for midnight operations off ZZZ and ZZZ1. I told ZZZ to hold their night departures because they instantly conflict with ZZZ1 departures. Then I gave ZZZ1 a departure release. About 4 minutes go by and I see a target climbing off of ZZZ. I get a call from ZZZ apologizing for launching an aircraft. On initial contact I turn the ZZZ departure east to a 050 heading because my ZZZ1 departure is climbing fast. If I had not gotten communication when I did they could have potentially hit. As it was I believe standard separation was still lost between the two departures. ZZZ failed to follow a control instruction resulting in an unsafe situation.The noise abatement departure off ZZZ and ZZZ1 are designed in a way that they automatically conflict. I would not be surprised if there is a long history of conflicts like this.
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.