DEN00LA132 · Spencer LONG EZE
Spencer LONG EZE · Accident: airframe, component or system failure during initial climb
From Four Corners Regional Airport (FMN) to Four Corners Regional Airport (FMN)
Event
- NTSB case
- DEN00LA132
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Spencer LONG EZE
- Aircraft type
- Spencer LONG EZE
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N51EZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Four Corners Regional Airport (FMN)To Four Corners Regional Airport (FMN)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Cooling system › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
When the pilot started the engine, he noticed the coolant temperature was 'slightly warm.' During taxi, coolant temperature increased. The pilot used full power for the high density altitude takeoff from runway 25. The engine overheated, the coolant recovery system failed, and steam entered the cockpit. The rear seat passenger was burned on the hip and back, thought there was a fire, and told the pilot to shut down the engine. The airplane was at an altitude of 700 feet. He secured the engine, turned the airplane around, and glided towards the airport. He declared an emergency, and was cleared to land on runway 5. A water hose broke at this time, and the steam dissipated. The airplane landed on airport property but with the nose landing gear retracted. When the airplane contacted soft dirt the main landing gear was torn off, and it skidded 200 feet, crossed a taxiway, and skidded another 200 feet before coming to a halt.
Probable cause
Failure of the coolant recovery system, resulting in overheating of the engine. A factor was the soft ground on which the forced landing was made.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00LA132
- Event ID
- 20001212X21440
- Case number
- DEN00LA132
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 18a1164c0a0f048ea48c27c0620d4bbe2b2be71fe578fd5ee384d88dea932583; retrieved 2026-09-21T20:09:22.936Z.