Narrative:

I was cpc-it training on local control; the active runway was 33 only; and runway 19 was closed. A C162 was straight in on the localizer/DME runway 33 approach; VFR practice; and intended on completing the approach and staying in the close traffic pattern. The C162 was issued 'cleared for the option;' a C180 was on a mid-field right downwind instructed to 'extend downwind' and was issued traffic to follow and advise when traffic was insight. The C180 said 'cessna insight'; local control then instructed the C180 to 'follow the cessna runway 33 cleared to land'. Local control received an accurate read back from the C180. The C162 crossed the runway threshold high but continued with descent for 'the option'. The C162 landed and the C180 turned a very close in base and was short final. Local control instructed the C162 to 'start your go traffic short final' the C162 reported 'we're rolling'. The C162 was rolling; local control anticipated them being airborne before the C180 crossed the threshold and did not send the C180 around. The C162 then stopped and said (in effect) 'we just lost our engine'. As the C162 was transmitting the C180 crossed the threshold of runway 33 and landed. By the C162 stating they were 'rolling' during a possible touch and go or stop and go maneuver that would make them a departure aircraft. When the C162 stopped on the runway with a 'failed engine'; transmitted their status effectively making the frequency unavailable; local control was unable to send the C180 around. Closest approximate proximity between both aircraft was 4;300 ft. It is recognized that local control was incorrect in issuing 'the option' to the C162 ensuring minimum runway occupancy time. Recommendation; add in the aim what standard same runway arrival/arrival and arrival/departure separation is as defined.

Google
 

Original NASA ASRS Text

Title: Tower Controller described a loss of separation event when traffic on an 'option' approach clearance; lost an engine; resulting in a separation issued with an aircraft landing.

Narrative: I was CPC-IT training on Local Control; the active runway was 33 only; and Runway 19 was closed. A C162 was straight in on the LOC/DME Runway 33 Approach; VFR practice; and intended on completing the approach and staying in the close traffic pattern. The C162 was issued 'Cleared for the option;' a C180 was on a mid-field right downwind instructed to 'extend downwind' and was issued traffic to follow and advise when traffic was insight. The C180 said 'Cessna insight'; Local Control then instructed the C180 to 'follow the Cessna Runway 33 cleared to land'. Local Control received an accurate read back from the C180. The C162 crossed the runway threshold high but continued with descent for 'the option'. The C162 landed and the C180 turned a very close in base and was short final. Local Control instructed the C162 to 'start your Go traffic short final' the C162 reported 'we're rolling'. The C162 was rolling; Local Control anticipated them being airborne before the C180 crossed the threshold and did not send the C180 around. The C162 then stopped and said (in effect) 'we just lost our engine'. As the C162 was transmitting the C180 crossed the threshold of Runway 33 and landed. By the C162 stating they were 'rolling' during a possible touch and go or stop and go maneuver that would make them a departure aircraft. When the C162 stopped on the runway with a 'failed engine'; transmitted their status effectively making the frequency unavailable; Local Control was unable to send the C180 around. Closest approximate proximity between both aircraft was 4;300 FT. It is recognized that Local Control was incorrect in issuing 'the option' to the C162 ensuring minimum runway occupancy time. Recommendation; add in the AIM what standard same runway arrival/arrival and arrival/departure separation is as defined.

Data retrieved from NASA's ASRS site as of July 2013 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.