Ase tower controller reported an aircraft on final was instructed to go-around; yet decided to land ...

Attributes
ACN	1411555
Time
Date	201612
Local Time Of Day	1201-1800
Place
Locale Reference	ASE.Tower
State Reference	CO
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	None
Flight Plan	VFR
Aircraft 2
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 135
Flight Phase	Taxi
Route In Use	None
Flight Plan	IFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Procedural Landing Without Clearance Ground Incursion Runway

Narrative:

I was working controller in charge [controller in charge] during the event. Aircraft X was on left downwind to land runway 15 while aircraft Y was within 3 mile final cleared to land runway 15. Local control had aircraft X get aircraft Y in sight and was told to follow the traffic; caution wake turbulence; and cleared to land runway 15. Aircraft Y landed and was told to exit the runway without delay. Aircraft Y ended up rolling past A5 and had to take A6 which is 1000 feet more runway. Local control observed aircraft X was too close and aircraft Y would not be off the runway and gave aircraft X a go-around on very short final. The pilot asked to say again and local control gave the go-around instruction again. Aircraft X did not execute a go-around and landed on the runway while aircraft Y was still on the runway between A5 and A6. Aircraft X exited A3 and there was no chance the aircraft would collide; however there was a loss of runway separation. After aircraft X landed he mentioned that there must have been an engine sputter. Aircraft X was given a brasher warning to call the tower. The flm took the call and the pilot explained he had a carb issue and when he tried to go around the engine sputtered and he was unable to go-around and instead landed.technically no emergency was declared but with a last second engine sputter there was no other option for the pilot except to continue the approach and land. Local control tried to fix the situation with a go-around; twice; and once I saw aircraft X was committed to landing I determined that the landing would be safe and the aircraft would not collide and took no further action except to have the pilot call the tower.

Original NASA ASRS Text

Title: ASE Tower Controller reported an aircraft on final was instructed to go-around; yet decided to land due to a sputtering engine. The previous arrival aircraft was still on the runway when the aircraft touched down.

Narrative: I was working CIC [Controller In Charge] during the event. Aircraft X was on left downwind to land runway 15 while Aircraft Y was within 3 mile final cleared to land runway 15. LC had Aircraft X get Aircraft Y in sight and was told to follow the traffic; caution wake turbulence; and cleared to land runway 15. Aircraft Y landed and was told to exit the runway without delay. Aircraft Y ended up rolling past A5 and had to take A6 which is 1000 feet more runway. LC observed Aircraft X was too close and Aircraft Y would not be off the runway and gave Aircraft X a go-around on very short final. The pilot asked to say again and LC gave the go-around instruction again. Aircraft X did not execute a go-around and landed on the runway while Aircraft Y was still on the runway between A5 and A6. Aircraft X exited A3 and there was no chance the aircraft would collide; however there was a loss of runway separation. After Aircraft X landed he mentioned that there must have been an engine sputter. Aircraft X was given a brasher warning to call the tower. The FLM took the call and the pilot explained he had a carb issue and when he tried to go around the engine sputtered and he was unable to go-around and instead landed.Technically no emergency was declared but with a last second engine sputter there was no other option for the pilot except to continue the approach and land. LC tried to fix the situation with a go-around; twice; and once I saw Aircraft X was committed to landing I determined that the landing would be safe and the aircraft would not collide and took no further action except to have the pilot call the tower.

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.

Ase tower controller reported an aircraft on final was instructed to go-around; yet decided to land due to a sputtering engine. The previous arrival aircraft was still on the runway when the aircraft touched down.