WPR10LA413 · Grumman Acft ENG COR-Schweizer G-164B
Crawford Aviation Services Grumman Acft ENG COR-Schweizer G-164B · Accident: powerplant system/component malfunction/failure during takeoff
From Buckeye, AZ to Buckeye, AZ
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10LA413
- 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
- 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
- N6607Q
- Operator
- Crawford Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Buckeye, AZTo Buckeye, AZ
- 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 · 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
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial Possible conflict
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had flown the airplane about 4.2 hours on the date of the accident with no discrepancies noted. During the accident takeoff, the pilot noted normal acceleration, engine indications, and tail liftoff. After completing 2/3 of the takeoff roll, the engine rpm increased to 2,600-2,700 (the maximum allowable is 2,550 rpm). The pilot felt a moderate-to-severe vibration and immediately initiated procedures for an aborted takeoff. He retarded the throttle to idle, applied maximum braking, and held the control stick full aft. As the airplane slowed to 20-30 knots, he steered the airplane away from a fence at the end of the runway onto hard packed desert terrain. After rolling a short distance, the left main landing gear encountered a depression in the terrain and sheared off. The airplane settled onto the left wing and was almost immediately engulfed in fire. Fire consumed the cabin and inboard wing areas, as well as the aft section of the engine, which exposed the gears in the accessory section. Fire consumed all accessories, including both magnetos. A postaccident examination of the engine could not determine a reason for the increase in rpm and vibration due to fire damage.
Probable cause
An increase in engine rpm and vibration, which resulted in an aborted takeoff and runway excursion. The reason for the increased engine rpm and vibration could not be determined because of postaccident fire damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA413
- Event ID
- 20100819X71659
- Case number
- WPR10LA413
- 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: 6031f73b8d71caeb69f69ed6799a79dea0b6caa3755254d338d868a94eb980d5; retrieved 2026-09-15T14:53:26.475Z.