LAX08CA082 · Grumman-Schweizer G-164B
Grumman-Schweizer G-164B · Accident: loss of control in flight during initial climb
From Port of Whitman Business Air Center Airport (S94) to S94
Event
- NTSB case
- LAX08CA082
- 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-Schweizer G-164B
- Aircraft type
- Grumman Schweizer 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
- N63D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Port of Whitman Business Air Center Airport (S94), Colfax, WATo S94
- 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 137: Agricultural
- 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
- Initial climb
- 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
- Loss of control in flight
- 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
- Wire; Pole
- 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 › Aircraft oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said that he was departing for an aerial application flight on runway 25 with a 12- to 15-knot tailwind. He had 1,400 pounds of dry fertilizer in the hopper. Takeoff from this airport must be in one direction due to climbing terrain and runway slope. He started a right turn down a valley when he felt a loss of lift. He started to dump his applicant, but the weight transfer was too slow. The airplane descended into power lines and impacted the ground. It continued through a fence and impacted a light pole.
Probable cause
The pilot's inadequate compensation for the wind conditions, failure to attain and maintain an adequate airspeed that resulted in a stall mush, and, the subsequent failure to maintain terrain and obstacle clearance during the takeoff initial climb. Contributing factors were the tailwind weather condition, and the one-way direction requirements of the airstrip.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA082
- Event ID
- 20080422X00531
- Case number
- LAX08CA082
- 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, coordinates. 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: c5a2da1fb396bef34c1edf0e72e74b2f0334b5c190e5b9aa458a063a4a9994f0; retrieved 2026-09-15T09:34:06.027Z.