37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 935089 |
Time | |
Date | 201103 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | Beechjet 400 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | King Air C90 E90 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Departure Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Narrative:
Runway xx [was] in use. A BE40 was completing an ILS approach to runway yy and then continuing with an IFR flight plan to end with a military BE90 departing runway xx westbound. Tower asked approach if they could send the BE40 on course on an approximate 060 heading; approach approved the request. Tower cleared the BE90 for take off runway xx when the BE40 was on a 3 mile final to runway yy. The BE40 went missed approach flying northeast bound over runway yy with the BE90 climbing opposite direction underneath the BE40. Opposite direction traffic merged with approximately 300 ft between the two aircraft. I advised the flm in the TRACON; observing that this was dangerous and needed to be brought to the local controller's attention. The flm said that they were probably using visual separation and it probably didn't look that bad out the window. The tower airplanes were head on with one climbing under the other aircraft over the runway. This is not the only example of dangerous situations being brought to the flm (all of them) attention and they just ignore the issues. If these problems are not corrected; there will be a major error or accident in the near future. Recommendation: the flm's here need to have a more active role in identifying dangerous situations and correct the controllers mistakes instead of trying to be their friends and looking the other way all the time.
Original NASA ASRS Text
Title: TRACON Controller described a head on situation between two Tower controlled aircraft; complained to the supervisor who indicated visual separation was likely being applied; the reporter claiming supervisors are not doing their job.
Narrative: Runway XX [was] in use. A BE40 was completing an ILS approach to Runway YY and then continuing with an IFR flight plan to END with a Military BE90 departing Runway XX westbound. Tower asked Approach if they could send the BE40 on course on an approximate 060 heading; approach approved the request. Tower cleared the BE90 for take off Runway XX when the BE40 was on a 3 mile final to Runway YY. The BE40 went missed approach flying northeast bound over Runway YY with the BE90 climbing opposite direction underneath the BE40. Opposite direction traffic merged with approximately 300 FT between the two aircraft. I advised the FLM in the TRACON; observing that this was dangerous and needed to be brought to the Local Controller's attention. The FLM said that they were probably using visual separation and it probably didn't look that bad out the window. The tower airplanes were head on with one climbing under the other aircraft over the runway. This is not the only example of dangerous situations being brought to the FLM (all of them) attention and they just ignore the issues. If these problems are not corrected; there will be a major error or accident in the near future. Recommendation: The FLM's here need to have a more active role in identifying dangerous situations and correct the Controllers mistakes instead of trying to be their friends and looking the other way all the time.
Data retrieved from NASA's ASRS site as of April 2012 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.