37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 926255 |
Time | |
Date | 201101 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Tower |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown |
Narrative:
A CRJ7 was departing on a SID with traffic in opposite direction [on] final; call sign and aircraft type unknown. I was providing visual separation between the two aircraft. Traffic was exchanged multiple times. I believe the aircraft on final had the crj in sight. The crj started the westbound turn required by the SID out of 9;600 ft MSL instead of 9;100 ft MSL that the departure procedure calls for (not uncommon for pilots to do); putting the aircraft behind the aircraft on final. The pilot of the crj later called the tower and said that they never did get the airport in sight and that they had to fly into clouds to avoid traffic. I had both aircraft in sight and did not observe the crj flying into clouds. The pilot never said anything during the operation. Opposite direction traffic at ZZZ is an operation that puts aircraft in close proximity with each other. More traffic could have been exchanged. If the tower is providing visual separation between arrivals and departures; to ensure separation; aircraft are instructed to stay on the 340 heading and not start their turn if an aircraft on final is not descending quickly enough. I think that this is the only logical way to run the operation in ZZZ. I do not believe that the situation was out of the 'norm' for this airport.
Original NASA ASRS Text
Title: Tower Controller providing visual separation during opposite direction landing and departing traffic indicated that post flight communications indicated the landing traffic encountered IMC conditions; the reporter noting never losing sight of both aircraft.
Narrative: A CRJ7 was departing on a SID with traffic in opposite direction [on] final; call sign and aircraft type unknown. I was providing visual separation between the two aircraft. Traffic was exchanged multiple times. I believe the aircraft on final had the CRJ in sight. The CRJ started the westbound turn required by the SID out of 9;600 FT MSL instead of 9;100 FT MSL that the departure procedure calls for (not uncommon for pilots to do); putting the aircraft behind the aircraft on final. The pilot of the CRJ later called the Tower and said that they never did get the airport in sight and that they had to fly into clouds to avoid traffic. I had both aircraft in sight and did not observe the CRJ flying into clouds. The pilot never said anything during the operation. Opposite direction traffic at ZZZ is an operation that puts aircraft in close proximity with each other. More traffic could have been exchanged. If the Tower is providing visual separation between arrivals and departures; to ensure separation; aircraft are instructed to stay on the 340 heading and not start their turn if an aircraft on final is not descending quickly enough. I think that this is the only logical way to run the operation in ZZZ. I do not believe that the situation was out of the 'norm' for this airport.
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.