Grumman Acft Eng G-164A accident near Hazelton, Idaho, August 18, 2008
On August 18, 2008 at about 3:05 pm local time, a Grumman Acft Eng G-164A, registered N6702Q, was substantially damaged in an accident during takeoff near Hazelton, Idaho (Hazelton Muni airport). It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 18, 2008 · about 3:05 pm local time
- Place
- Hazelton, Idaho · Hazelton Muni · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Grumman Acft Eng G-164A
- Registration
- N6702Q · no longer on the register · serial 1707
- Damage
- Substantial damage
- Flight
- Aerial application (crop spraying) flight · agricultural flying rules (Part 137)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during takeoff defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- factor Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Contributed to outcome
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Crosswind correction › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- Environmental issues › Physical environment › Object/animal/substance › Pole › Not specified
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land
- Flight time: 954 hours in all; 208 in this make and model; 419 in the last 90 days; 190 in the last 30 days
- Last flight review: April 1, 2008
- Medical certificate: Class 2
The aircraft
- Landing gear: fixed
- Engine: Honeywell TPE331 (turboprop); 0 hours total
The flight
- Departed from: U94 Hazelton ID
- Flight plan: none
- Runway 24, 2,800 ft by 90 ft
Weather at the time
- Light: daylight
- Wind: from 050° at 13 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 36°F (2°C)
- Altimeter: 29.94 inHg
- Observation at 2:53 pm from JER, 16 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N6702Q the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.