 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ama controller described a near conflict event when the local controller released opposite direction traffic requiring immediate action by the reporter to secure separation.
| Attributes | |
| ACN | 888128 |
| Time | |
| Date | 201005 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | AMA.Airport |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Supervisor / CIC Flight Data / Clearance Delivery Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
I was on radar and requested from local control that air carrier X be allowed to land on runway 04 per pilot request (non-active runway). Local control approved the request and I vectored aircraft for the right base entry to runway 04 and spaced runway 22 aircraft to allow for the operation. When air carrier X reported the runway in sight at 8 NM south at 7500 ft; I cleared the aircraft for visual approach and switched aircraft to local control frequency. Apparently local control performed a position relief briefing during this time; because shortly after I switched air carrier X to local control; the new controller coordinated a runway 22 departure; the aircraft rolled and was restricted at 6000 ft and heading 130 degrees for the air carrier X arrival. This restriction placed the two aircraft on a collision course since air carrier X was on a visual approach with no altitude restriction. Corrective action taken: I immediately told the departure to turn left heading 090 and climb and maintain 170 and issued traffic. He reported the E145 in sight and I advised him to maintain visual separation. Recommendation; increase operational staffing at facility to the normal staffing levels so that the flms (front line managers) can do their job and have proficient cpc's on the operational positions during busy traffic sessions.
Original NASA ASRS Text
Title: AMA Controller described a near conflict event when the Local Controller released opposite direction traffic requiring immediate action by the reporter to secure separation.
Narrative: I was on RADAR and requested from Local Control that Air Carrier X be allowed to land on Runway 04 per pilot request (non-active runway). Local Control approved the request and I vectored aircraft for the right base entry to Runway 04 and spaced Runway 22 aircraft to allow for the operation. When Air Carrier X reported the runway in sight at 8 NM South at 7500 FT; I cleared the aircraft for visual approach and switched aircraft to Local Control frequency. Apparently Local Control performed a position relief briefing during this time; because shortly after I switched Air Carrier X to Local Control; the new Controller coordinated a Runway 22 departure; the aircraft rolled and was restricted at 6000 FT and heading 130 degrees for the Air Carrier X arrival. This restriction placed the two aircraft on a collision course since Air Carrier X was on a visual approach with no altitude restriction. Corrective Action Taken: I immediately told the departure to turn left heading 090 and climb and maintain 170 and issued traffic. He reported the E145 in sight and I advised him to maintain visual separation. Recommendation; increase operational staffing at facility to the normal staffing levels so that the FLMs (Front Line Managers) can do their job and have proficient CPC's on the operational positions during busy traffic sessions.
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.