LAX82FUJ26 · Beachner QUICK SILVER QUICK SILV
Beachner QUICK SILVER QUICK SILV · Accident: total loss of engine power (mechanical failure) en route
From Kingman Airport (IGM) to Kingman Airport (IGM)
Event
- NTSB case
- LAX82FUJ26
- 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
Beachner QUICK SILVER QUICK SILV
- Aircraft type
- Beachner QUICK SILVER
- 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
- N824CB
- Operator
- Chris Beachner
- Onboard fatalities
- Unknown
- Route
- From Kingman Airport (IGM), Kingman, AZTo Kingman Airport (IGM), Kingman, AZ
- 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 · climb to 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
- Engine assembly, bearing › Overtemperature
- Fluid, oil › Contamination
- Fluid, oil › Starvation
- Pilot in command › Maintenance, overhaul, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER CLIMBING UP TO PATTERN ALTITUDE THE ENGINE LOST POWER. THE PILOT MADE A TURN BACK TOWARDS THE AIRPORT WHILE TRYING TO RESTART THE ENGINE BUT HAD TO LAND IN AN OLD B-17 PARKING AREA. THE AIRCRAFT STRUCK A FENCE AND DITCH DURING ROLLOUT AND NOSED OVER. ENGINE DISASSEMBLY RE VEALED THAT THE MAIN AND CONNECTING ROD BEARINGS SHOWED EVIDENCE OF OIL STARVATION. FURTHER EXAMINATION REVEALED THAT THE DRILLED OIL PASSAGES WERE PLUGGED WITH A GRITTY MATERIAL IDENTIFIED BY THE OWNER AS MACHINE SHOP GLASS BEAD GRIT THAT HAD BEEN USED BY THE OWNER DURING OVERHAUL FOR CLEANING SOME ENGINE PARTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82FUJ26
- Event ID
- 20020917X02296
- Case number
- LAX82FUJ26
- 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: 49a02dcf9d2a2d171551d758b0dfa82442e8989ba5f4597d502138f62e99436e; retrieved 2026-09-22T03:11:46.803Z.