SEA08CA183 · Grumman Acft Eng G-164A
Grumman Acft Eng G-164A · Accident: loss of control in flight during takeoff
From Hazelton Municipal Airport (U94) to an unrecorded destination
Event
- NTSB case
- SEA08CA183
- 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 G-164A
- Aircraft type
- Grumman Acft Eng 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
- N6702Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hazelton Municipal Airport (U94), Hazelton, IDTo 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 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
- 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
- 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
- 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 he was departing for the fourth aerial application of the day and the airplane stalled at the end of the runway. The right wings struck a post and the airplane turned 90 degrees to the right. The airplane came to rest about 200 yards from the end of the runway. The ground crew stated that a strong tailwind had developed about the time the pilot was departing.
Probable cause
The pilot's inadequate compensation for the tailwind and failure to attain and maintain airspeed, which resulted in an inadvertent stall. The tailwind was a contributing factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08CA183
- Event ID
- 20080917X01480
- Case number
- SEA08CA183
- 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: 4616003a0f18201fdf80c0f7d3110a2b87c4bad9874ebd25c1be7ebcf1e34092; retrieved 2026-09-15T10:14:03.800Z.