An ANC controller described a loss of separation event occuring when a take off clearance was issued to Runway 25R traffic with Runway 14 landing traffic still on the runway. Photo mission distractions were listed as causal factors.
Synopsis
An ANC controller described a loss of separation event occuring when a take off clearance was issued to Runway 25R traffic with Runway 14 landing traffic still on the runway. Photo mission distractions were listed as causal factors.
Narrative
Air Carrier X landed Runway 14 and was at taxi speed. Since there was no reason to withhold departure clearance; I cleared Air Carrier Y for Take-Off; checking the position and status of another aircraft flying a grid pattern overhead the field at one thousand eight hundred. Another Air Carrier checked on frequency. I then instructed Air Carrier X to exit the runway. Approximately nine seconds elapsed from the time Air Carrier Y completed his read back to the time I instructed Air Carrier X to exit. Traffic was somewhat complex due to an aircraft's mapping mission. [They were] flying lines with very wide teardrop turns at relatively low altitude for several hours. We did not have staffing available for a Local Assist. I have reviewed the 7110.65 and been instructed by my Operations Manager that I cannot anticipate the aircraft will be able to exit in a timely fashion even though it appears under control. Unless we allow anticipated separation to be used for exiting aircraft; all I can do is ensure the aircraft has acknowledged runway exiting instructions prior to clearing the departure for Take-Off. We can educate the controller(s) who actually saw the event developing to speak up in a timely fashion.
Second reporter narrative
I was OSIC (Operations Supervisor in Charge) and due to a summer-long construction project; Runway 7R/25L was closed. Runway 7L/25R intersects with the Runway 32/14. Because of wind we were landing Runway 14 and departing Runway 25R. During this configuration; when the airport arrival demand warrants; Airport Management will sometimes issue a NOTAM closing the south 487 feet of Runway 14 thereby 'eliminating' the intersection of the runways and allowing simultaneous operations. At times the runways intersect and at times they don't depending on if 'the NOTAM' is in place or not. This operational error occurred when Air Carrier X landed Runway 14 and Local subsequently issued takeoff clearance to Air Carrier Y on runway 25R. Air Carrier Y began departure roll before Air Carrier X and Local issued runway exit instructions to Air Carrier X immediately thereafter. With 'the NOTAM' in effect this would have been a legal operation. Without 'the NOTAM'; the arriving aircraft would have to have completed landing roll and be instructed to hold short of the intersection; or be turned off the runway after arrival; per the 7110.65. At the time if the incident 'the NOTAM' was not in effect so the runways did intersect. At the time of the incident I was keeping watch of a Piper Navajo on a photo mission. It was a mission that took the aircraft back and forth over the airport. There were many traffic calls to that aircraft and landing/departing aircraft that had to be accomplished. I was assisting in keeping up with the position of Photo aircraft.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.