BFO87DIG06 · Striplin SKY RANGER
Striplin SKY RANGER · Accident: total loss of engine power (mechanical failure) on approach
Event
- NTSB case
- BFO87DIG06
- 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
- 1 · 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
Striplin SKY RANGER
- Aircraft type
- Striplin SKY RANGER
- 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
- N4925S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Approach · VFR pattern downwind
- 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
- Destroyed
Cause areas
- Ignition system › Loose
- Maintenance › Improper
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER TAKING OFF ON A TEST FLT, THE PLT REMAINED IN THE TRAFFIC PATTERN & WAS ON DOWNWIND WHEN THE ENG SURGED OR SPUTTERED, THEN LOST POWER. SOON THEREAFTER, THE ACFT ENTERED A STEEP DSCNT & CRASHED. THE EXPERIMENTAL, HOME BUILT ACFT HAD ONLY 11 HRS OF FLT TIME. NO PREIMPACT PART FAILURE OR MALFUNCTION OF THE AIRFRAME WAS FND. HOWEVER, DISASSEMBLYOF THE ENG REVEALED THE BREAKER POINT MOUNTING PLATE & MACHINE SCREWS (BOLTS) WERE LOOSE. THE BOLTS HAD BACKED OUT OF THE THREADED HOLES & WERE BENT. ONE BOLT WAS LODGED BTN THE FLYWHEEL & THE ENG HOUSING, RESTRICTING ROTATION. THE LOOSE BREAKER POINT MOUNTING PLATE WAS PART OF THE IGNITION SYS. IT HAD BEEN INSTALLED ON THE ENG HOUSING WITH 2 BOLTS, WASH- ERS & LOCK WASHERS. RPRTDLY, THE LOCK WASHER(S) HAD BECOME FLAT, INDCG LOSS OF ELASTICITY (LOCKING ABILITY). PREVIOUSLY,THE FLT CTL SYS HAD INSUFFICIENT ELEV CTL AT HI & LOW PWR SETTINGS; TO CORRECT THIS, AN ELEV SPRING WAS INSTALLED & THE ELEV CABLE ATTACHMENT BRACKET WAS REPOSITIONED, BUT THE PREIMPACT COND OF THE ELEV CTL SYS WAS NOT VERIFIED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record BFO87DIG06
- Event ID
- 20001213X31118
- Case number
- BFO87DIG06
- 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: 9b84288b97146bf6f599ef45bf36c2386844814632e582d4d4274370302bcf49; retrieved 2026-09-21T04:06:13.270Z.