WPR14CA293 · Grumman Acft ENG COR-Schweizer G 164B B
Grumman Acft ENG COR-Schweizer G 164B B · Accident: abnormal runway contact during takeoff
From Marysville, CA to Marysville, CA
Event
- NTSB case
- WPR14CA293
- 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
Grumman Acft ENG COR-Schweizer G 164B B
- Aircraft type
- Grumman G-164
- 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
- N48475
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marysville, CATo Marysville, CA
- Aircraft age
- About 38 years (built 1976)
- 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 · rejected takeoff
- 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
- Abnormal runway contact
- 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
- Tree(s)
- 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
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that while on takeoff roll with the wind calm, he noticed that the airplane had failed to gain enough speed to lift off. He then added throttle and attempted to dump the load, but the dump-stop prevented him from jettisoning the load. The pilot stated that at the very end of the runway the airplane lifted off, followed by the tailwheel impacting a small ridge, which slowed the airplane. The aircraft subsequently cleared a ditch and then started impacting young trees, with large trees directly in front of him. The pilot added that he then pulled the power off and landed in a field of young trees. The upper and lower wing panels were substantially damaged. The pilot stated that the accident could have been prevented had he made sure that the dump stop was flipped over prior to takeoff, which would have allowed the load to be dumped faster. The pilot also stated that due to the temperature having increased from what it was earlier that morning, he should have reduced his chemical load. The density altitude at the time of the accident was calculated to be about 2,042 feet mean sea level (msl); the elevation of the airstrip was about 90 feet msl. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to adequately monitor the environmental conditions to assure the aircraft performance would afford an uneventful takeoff with the loading conditions. Contributing to the accident were the pilot's inability to jettison the load due to the dump lever being positioned inappropriately prior to takeoff, and the density altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA293
- Event ID
- 20140715X14629
- Case number
- WPR14CA293
- 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: 743946b3e27c16479ee65e0347bebbc8b8bcc225e5aa787fa6009cb1177f53ad; retrieved 2026-09-16T00:54:12.254Z.