CEN18LA156 · Laminar Lancair 360
Laminar Lancair 360 · Accident: fuel related en route
From Lee's Summit Municipal Airport (LXT) to Dalhart Municipal Airport (DHT)
Event
- NTSB case
- CEN18LA156
- 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
- Unknown
- 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
Laminar Lancair 360
- Aircraft type
- Laminar LANCAIR 360
- 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
- N92WL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lee's Summit Municipal Airport (LXT), Lee Summit, MOTo Dalhart Municipal Airport (DHT), Dalhart, TX
- Aircraft age
- About 2 years (built 2016)
- 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
- Defining eventThe 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
- Fuel related
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was conducting a personal flight with a pilot-rated passenger in an experimental, amateur-built airplane. The pilot reported that, during flight at 10,000 ft, the airplane experienced moderate to severe turbulence for a few seconds. Shortly after, the engine stopped producing power without warning. The pilot immediately attempted to restart the engine to no avail. He flew at best glide speed toward the nearest airport, located about 12 nautical miles away, but landed short of the runway in a pasture, during which the airplane encountered sagebrush, which caused the landing gear to collapse as the airplane bounced and skidded to a stop; the fuselage sustained substantial damage.
The examination of the airplane at the accident site revealed that the emergency fuel shutoff valve, which was located on the right side of the center console under the instrument panel, was about 1/4 of the way between the on (horizontal) position and the off (vertical) position. The valve could not be seen by the pilot. Further, the pilot-rated passenger stated that he could not see the emergency fuel shutoff valve. He was not sure if his knee hit the valve handle and shut off the fuel flow from the header fuel tank to the engine during the turbulence event. The onboard flight and engine monitoring system indicated that the airplane was about 10,000 ft mean sea level when it experienced about a 2g vertical acceleration. The engine data indicated a rapid decrease of fuel flow after the 2g acceleration with a coinciding decrease in exhaust gas temperatures and fuel pressure.
About 30 gallons of fuel was drained from the airplane before it was transported to the recovery facility. An engine examination and test run were conducted, and the engine performed satisfactorily. A second test was conducted to determine the effectiveness of the emergency fuel shut off valve and where it needed to be positioned before it cut off all fuel to the engine. There was no indication of a power loss until the valve handle was in the full vertical position, which then caused the engine to stop within about 10 seconds.
The pilot-rated passenger reported that he had recently purchased the airplane and that he and the pilot were flying the airplane to his home base. He stated that although he and the pilot were experienced pilots, neither had any flight time in the airplane except for the orientation flight that the pilot had received.
Given the engine data, it is likely that the pilot-rated passenger's knee inadvertently hit the emergency fuel shutoff valve during the turbulence event and caused it to shut off the fuel flow from the header tank to the engine. Further, had the pilot been familiar with the airplane, he would have known where the fuel selector valve was, regardless of whether it was easy to see, and would have checked it when the engine lost power as a memory item check in the emergency procedures.
Probable cause
The pilot-rated passenger’s inadvertent contact with and closure of the emergency fuel shutoff valve, which resulted in the total loss of engine power due to fuel starvation. Contributing to the accident was the pilot's lack of experience in the accident airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA156
- Event ID
- 20180503X85948
- Case number
- CEN18LA156
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 2cbef4e1d384b40055a49b4edf048bf5052d8131eca35a7a9bae6868f0ef2165; retrieved 2026-09-16T07:00:37.916Z.