FTW98LA302 · Keith TEAM MINI MAX 1600R TEAM MINI
Keith TEAM MINI MAX 1600R TEAM MINI · Accident: total loss of engine power (mechanical failure) en route
From T02 · Houston, TX to DICKENSON, TX (no airport)
Event
- NTSB case
- FTW98LA302
- 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
Keith TEAM MINI MAX 1600R TEAM MINI
- Aircraft type
- Keith TEAM MINI MAX 1600R
- 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
- N106BK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From T02 · Houston, TXTo DICKENSON, TX (no airport)
- 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
- En route · cruise
- 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
- Total loss of engine power (mechanical 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
The pilot was en route and approximately 7 miles from his destination airport, when he observed 'a rise in the cylinder head temperature of the number 1 cylinder.' He attempted to control the temperature by 'coming completely out of the throttle and then going back to full throttle.' At 1,200 feet AGL, the Rotax 503 engine lost power. The pilot stated that he immediately 'put the plane into the best glide rate' and landed the aircraft in a field 'without problems.' During the landing roll, the right wing struck a steel object which was obscured by weeds. Examination of the engine by the owner revealed that the lost of engine power was the result of engine overheating due to the failure of the fan belt to the engine cooling fan.
Probable cause
The loss of engine power as result of the failure of the cooling fan belt. A factor was the lack of suitable terrain for the pilot to execute the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA302
- Event ID
- 20001211X10573
- Case number
- FTW98LA302
- 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: 5fe4ae03393ca3dbec87f753898d5a1b31705cf8b14a7a8a2162d84683a0881a; retrieved 2026-09-22T17:34:35.262Z.