CHI85LA047 · Rockwell 114
Rockwell 114 · Accident: propeller/rotor contact to person during takeoff
From 1G6 · STRONGVILLE, OH to 226 · Lorain, OH
Event
- NTSB case
- CHI85LA047
- 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
Rockwell 114
- Aircraft type
- Rockwell 114
- 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
- N4739W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 1G6 · STRONGVILLE, OHTo 226 · Lorain, OH
- 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
- Takeoff · roll/run
- 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/rotor contact to person
- 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/mush
- 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 performance, climb capability › Deteriorated
- Pilot in command › Aircraft handling, improper
- Pilot in command › Stall/mush, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PLT WAS AWARE RUNWAY HAD A PRONOUNCED DIP JUST PRIOR TO ROTATION AREA OF HIS ACFT. PASSING THE DIP ON TAKEOFF ROLL, HE FELT A 'SHIMMY' WHICH HE ATTRIBUTED TO NOSE GEAR REACTION TO THE DIP. PLT CONSIDERED ABORTING TAKEOFF, BUT FELT INSUFFICIENT RUNWAY REMAINED. ON INITIAL CLIMB, ACFT BEGAN SEVERE VIBRATION, CLIMB ABOVE 100 FT AGL NOT POSSIBLE PLT MANEUVERED TO AVOID TALL TREES IN WOODED AREA AHEAD BUT COULD NOT MAINTAIN SAFE ALTITUDE AND AIRSPEED; ALLOWED THE ACFT TO STALL/MUSH INTO TREES. PLT STATED INITIAL CHECKOUT IN MAKE/MODEL INCLUDED INSTRUCTIONS TO 'HOLD NOSE ON GROUND UNTIL REACHING 90 KTS.' FAA INSPECTOR STATED THIS SPEED IS EXCESSIVE AND WILL CAUSE THE ACFT TO 'WHEELBARROW.' INVESTIGATION REVEALED NOSEDOWN TRIM SETTING, PROP MARKS ON RWY AND ALL PROP BLADES BENT REARWARD 4 INCHES FROM TIPS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI85LA047
- Event ID
- 20001214X41536
- Case number
- CHI85LA047
- 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: df0abc25c9e465e34ee5f7a166e82e1db17c6ffc4aa643f8faa5c92db72ccc48; retrieved 2026-09-22T02:02:58.921Z.