CEN11CA551 · Quicksilver SPRINT II
Quicksilver SPRINT II · Accident: fuel exhaustion while maneuvering
From Pilot Pointe Estates Airport (SN52) to Pilot Pointe Estates Airport (SN52)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11CA551
- 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
Quicksilver SPRINT II
- Aircraft type
- Quicksilver SPRINT
- 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
- N403BP
- Operator
- Patterson Kenneth M
- Onboard fatalities
- Unknown
- Route
- From Pilot Pointe Estates Airport (SN52), Douglass, KSTo Pilot Pointe Estates Airport (SN52), Douglass, KS
- 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
- 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 exhaustion
- 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 › Aircraft oper/perf/capability
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, while conducting a local flight, the airplane's engine began to lose power. The pilot was unable to maintain altitude and the airplane began to descend. The pilot initially chose a field in which to land, but a barbed wire fence obstructed the selected landing area. The pilot then attempted to land past the barbed wire fence; however, the airplane stalled and impacted terrain. The hard landing resulted in substantial damage to the fuselage and wings. An examination of the airplane revealed a lack of fuel throughout the fuel system. After adding fuel to the airplane's fuel tanks, the engine operated normally.
Probable cause
The pilot’s improper fuel management, which resulted in a loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA551
- Event ID
- 20110808X91301
- Case number
- CEN11CA551
- 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: 390f934ea23d5adeec61e7889001c994a4bfaa5a4df35ffbf55b798ad8d8b4a7; retrieved 2026-09-15T16:35:00.677Z.