37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1454345 |
Time | |
Date | 201706 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | GTF.Tower |
State Reference | MT |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
I was working approach with a trainee. We had switched aircraft X to tower making a straight in to runway 17. Runway 3 was advertised. The local controller; who was also the controller in charge (controller in charge) at the time; requested a turn for aircraft Y to depart off runway 3. I heard the local controller then issue aircraft Y a takeoff clearance. I turned to the local controller and brought it to his attention that aircraft Y had to be through the intersection prior to aircraft X crossing the threshold. His response to me was that he did not because the aircraft X was a full stop; which is inaccurate. The incident was not reported by the controller in charge.this is the second time I have witnessed this type of event in the last couple weeks with our newly reopened crossing runway. I would suggest facility recurrent/refresher training on intersecting runway separation requirements.
Original NASA ASRS Text
Title: An Approach Controller reported that a Local Controller cleared an aircraft to land; while another aircraft was cleared for takeoff from a converging non-intersecting runway.
Narrative: I was working Approach with a trainee. We had switched Aircraft X to Tower making a straight in to Runway 17. Runway 3 was advertised. The Local Controller; who was also the Controller in Charge (CIC) at the time; requested a turn for Aircraft Y to depart off Runway 3. I heard the Local Controller then issue Aircraft Y a takeoff clearance. I turned to the Local Controller and brought it to his attention that Aircraft Y had to be through the intersection prior to Aircraft X crossing the threshold. His response to me was that he did not because the Aircraft X was a full stop; which is inaccurate. The incident was not reported by the Controller in Charge.This is the second time I have witnessed this type of event in the last couple weeks with our newly reopened crossing runway. I would suggest facility recurrent/refresher training on intersecting runway separation requirements.
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.