CHI04LA217 · Grumman G-164-B
Grumman G-164-B · Accident: overrun during landing
From Fenton, IL to Bradford, IL
Event
- NTSB case
- CHI04LA217
- 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 G-164-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
- N6677Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fenton, ILTo Bradford, IL
- 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
- Landing · landing roll
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Distance/speed, misjudged
- Pilot in command › Go-around, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage when it contacted a ditch and nosed over after it overran the end of a 2,400 foot grass airstrip. The pilot reported that he circled the grass airstrip once before setting up for a landing to the south on the north/south runway. He landed "as short on the north end as the railroad tracks would allow." He reported the brakes did not feel "as effective as normal." He pumped the brakes twice but they failed to slow the airplane. He reported that it was too late to "power-up and go around," and the airplane departed the end of the runway. The airplane hit a small ditch and it nosed over. The inspection of the brake system revealed the brakes operated normally. No mechanical deficiencies were observed. A witness reported the grass was wet due to a heavy dew on the morning of the accident. He reported that he observed the airplane on final approach for landing. He reported that the airplane was too high and it landed past the first one-third of the runway. He reported the pilot "used up quite a bit of runway before he touched down." He reported that there was no way the airplane was going to stop on the runway due to the dew on the grass and the speed of the airplane.
Probable cause
The pilot's misjudgment of speed and distance, and his failure to perform a go-around. Additional factors were the wet runway and the ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04LA217
- Event ID
- 20040903X01351
- Case number
- CHI04LA217
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 88400596ed0310323c537d8657d8cbd62bf25668c63f16e904515258460d61bc; retrieved 2026-09-22T06:55:08.906Z.