FTW95FA001 · McMurtrie JURCA MJ-10 JURCA MJ-1
McMurtrie JURCA MJ-10 JURCA MJ-1 · Accident: propeller failure/malfunction on approach
From Bartlesville Municipal Airport (BVO) to Bartlesville Municipal Airport (BVO)
Event
- NTSB case
- FTW95FA001
- 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
McMurtrie JURCA MJ-10 JURCA MJ-1
- Aircraft type
- Mcmurtrie JURCA MJ-10
- 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
- N379SF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bartlesville Municipal Airport (BVO)To Bartlesville Municipal Airport (BVO), OK
- 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 final
- 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
- Propeller failure/malfunction
- 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
- Stall
- 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
- Pilot in command › Airspeed, not maintained
- Pilot in command › Diverted attention
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT TOOK OFF AND REMAINED IN THE TRAFFIC PATTERN. WITNESSES SAID HE HAD DIFFICULTY LOWERING THE LANDING GEAR AND BY THE TIME IT WAS FULLY EXTENDED, THE AIRPLANE HAD TURNED FINAL AND WAS HALFWAY DOWN THE RUNWAY. WITNESSES SAID POWER WAS INCREASED, THE NOSE PITCHED UP, THE LEFT WING DROPPED, AND THE AIRPLANE DOVE OR SPUN TO THE GROUND. THE PILOT'S BROTHER SAID THAT ON A PREVIOUS TEST FLIGHT, THE PILOT HAD MADE A FORCED LANDING WHEN THE PROPELLER FEATHERED, AND IT APPEARED TO HIM THE SAME THING HAPPENED ON THIS FLIGHT. THE PROPELLER DISASSEMBLY REPORT INDICATED THE BLADE ANGLE WAS '40 DEGREES TO 45 DEGREES. . . CONSIDERED HIGH FOR A SLOW SPEED IMPACT.' THIS WOULD BE POSSIBLE IF 'THE CONFIGURATION'S OUTPUT CONTROL PRESSURE WAS NOT CAPABLE OF MAINTAINING BLADE ANGLE, AND THAT THE PROPELLER WAS SLIPPING TO COARSE PITCH.' NO OIL LEAKS NOR PROPELLER GOVERNOR ANOMALIES WERE FOUND.
Probable cause
AN INADVERTENT PILOT-INDUCED STALL AT TOO LOW AN ALTITUDE TO EFFECT A SAFE RECOVERY. FACTORS WERE THE MALFUNCTIONING PROPELLER SYSTEM AND THE UNCOMMANDED FEATHERING OF THE PROPELLER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95FA001
- Event ID
- 20001206X02421
- Case number
- FTW95FA001
- 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: aaa90606fd8ced15ec739bb0e4b54293fec90eb2136e7e2395975f5ab9536d98; retrieved 2026-09-20T23:59:30.493Z.