TRACON Controller described a loss of separation event between an IFR departure and an IFR practice missed approach; indicating the Local Controller should have coordinated for separation headings.
Synopsis
TRACON Controller described a loss of separation event between an IFR departure and an IFR practice missed approach; indicating the Local Controller should have coordinated for separation headings.
Narrative
I was working East Feeder RADAR position. A B737; departed the runway; flight progress strip showed aircraft on 340 heading. I called Local Control to confirm this heading and was told yes the B737 was given the turn. Following immediately after the B737 was a BE20; on an IFR practice approach. The BE20 had been coordinated to fly runway heading on departure. After issuing RADAR contact to the B737; I noticed the aircraft did not turn to the 340 heading. Then the BE20 checked in on departure with the B737 in sight. I then told the BE20 to maintain visual separation from the B737 and issued a right turn to 040. I realized when the B737 did not turn and the BE20 was right behind him a possible loss of separation may be occurring. I immediately took steps to re-establish separation. Make sure both Tower and TRACON Controllers are aware of what other operations are going on adjacent their respective areas of control. The Tower Controller could have coordinated a turn for the BE20 when he knew he was going to try and get the B737 out before the BE20's approach.
Second reporter narrative
I was working Flight Data/Clearance Delivery combined with Tower Controller in Charge. Local Control/Ground Control was combined. There were a total of two individuals in the Tower. Traffic was light to moderate; I was kept busy with numerous VFR call ups and full route clearances needing issued. A third controller was overlapping/monitoring Local Control from the Center Control position. A BE20; approaching a three mile final to the runway; practicing an RNAV approach. I observed 'GOH' in the scratch pad; indicating a standard climb out of runway heading; climbing to 3;000 FT; back to RADAR. I overheard Local Control clear a B737 for take off with 'traffic on a three mile final'. From my vantage the King Air was closer to two miles from the threshold. I stated verbally 'This isn't going to work'. I heard Local Control say; '!!!!; this isn't gonna work'. I fully expected Local Control to either cancel the B737 take off clearance; send the BE20 around; or some combination of the two. Instead; the B737 was told 'turn left heading 340; no delay on the roll out'. The BE20 was merely told to maintain visual separation with 'the traffic' while on short final for the approach. It was unclear to me whether the BE20 could maintain visual separation or whether he even had the departing traffic in sight. I visually observed the BE20 cross the threshold with the B737 approximately 4;000 FT down the runway. The B737 apparently never read back the turn instruction; so both aircraft were simply switched to Departure; runway heading climbing to 3;000 FT. To my knowledge Local Control never coordinated the use of visual separation with the RADAR Controller. My verbal recommendation to Local Control that he turn the BE20 to a heading of 040 was ignored. I believe he simply had no idea what to do.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.