 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Sts controller described an apparent loss of separation event when observing an aircraft initiating a go around because of departure traffic spacing.
| Attributes | |
| ACN | 965126 |
| Time | |
| Date | 201108 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | STS.Airport |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Cessna 340/340A |
| Flight Phase | Final Approach |
| Route In Use | None |
| Flight Plan | VFR |
| Aircraft 2 | |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Flight Plan | VFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery Ground Supervisor / CIC |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy |
Narrative:
At the time of this incident; I was working ground control/flight data/controller in charge combined and I was busy taxiing aircraft and augmenting/cutting the ATIS. I saw aircraft X; a twin cessna; off the departure end of runway 14 whom I assumed had done a low approach; touch and go; or go around. Aircraft X was at about 1;000 ft and appeared to be climbing 1/4 mile off the departure end of the runway. Behind the twin cessna; I witnessed aircraft Y; a bonanza whom I had taxied out shortly before; depart. I did not think anything was amiss because the bonanza had not entered the runway until the twin cessna was at least 3;000 ft down runway 14. Local control gave no indication that the twin cessna had gone around; because local had forgotten them and cleared the bonanza for takeoff; thus prompting the twin cessna to initiate their own go around. Whenever possible; [I recommend] having uncombined positions so that an extra pair of eyes/ears is possibly available to assist local control when traffic picks up.
Original NASA ASRS Text
Title: STS Controller described an apparent loss of separation event when observing an aircraft initiating a go around because of departure traffic spacing.
Narrative: At the time of this incident; I was working Ground Control/Flight Data/CIC combined and I was busy taxiing aircraft and augmenting/cutting the ATIS. I saw aircraft X; a twin Cessna; off the departure end of Runway 14 whom I assumed had done a low approach; touch and go; or go around. Aircraft X was at about 1;000 FT and appeared to be climbing 1/4 mile off the departure end of the runway. Behind the twin Cessna; I witnessed aircraft Y; a Bonanza whom I had taxied out shortly before; depart. I did not think anything was amiss because the Bonanza had not entered the runway until the twin Cessna was at least 3;000 FT down Runway 14. Local Control gave no indication that the twin Cessna had gone around; because Local had forgotten them and cleared the Bonanza for takeoff; thus prompting the twin Cessna to initiate their own go around. Whenever possible; [I recommend] having uncombined positions so that an extra pair of eyes/ears is possibly available to assist Local Control when traffic picks up.
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.