SEA98LA142 · Socata RALLYE 235E RALLYE 235
Socata RALLYE 235E RALLYE 235 · Accident: total loss of engine power (non-mechanical) while maneuvering
From Kalispell City Airport (S27) to FLATHEAD RIVER, MT
Event
- NTSB case
- SEA98LA142
- 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
Socata RALLYE 235E RALLYE 235
- Aircraft type
- Socata RALLYE 235
- 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
- N301RA
- Operator
- Thomas Mcintyre
- Onboard fatalities
- Unknown
- Route
- From Kalispell City Airport (S27), Kalispell, MTTo FLATHEAD RIVER, MT
- 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
- Maneuvering
- 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 (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- Pilot in command › Fuel management, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was a 'powder bombing' mission being conducted at a local fly-in. The pilot reported that in order to give his passenger, the 'bombardier', a closer view of the target (on a private airstrip along a river), he initiated an extended 30-degree bank right turn at approximately 500 feet above some trees in the area. He reported that at this time, the left wing tank was empty, the right wing tank contained 14 gallons of fuel, and the fuel selector was on right tank. He stated that 'fuel drained away from [the fuel] pump, [and the] engine died due to lack of fuel.' He stated he tried banking the plane left to restart the engine, but could not get it to restart. He then performed a forced landing in the river after deciding he would not be able to clear the trees to make the airstrip. The airplane's fuel selector was found set to right tank in post-accident examination, and no fuel was found in the line from the engine-driven fuel pump to the carburetor. After the engine was flushed and the magnetos dried, the engine was successfully test-run. Each of the airplane's two separated wing tanks has a 37-gallon capacity, with 35.66 gallons usable.
Probable cause
The pilot-in-command's improper fuel management, resulting in fuel starvation. Related factors were insufficient altitude available for effective remedial action, and lack of suitable terrain for a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA98LA142
- Event ID
- 20001211X10722
- Case number
- SEA98LA142
- 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: a5aeb6eb89ff2b651a1d4d04f2f45618f28d700bf53fc61c7b2de4aa76cae764; retrieved 2026-09-22T17:25:19.916Z.