FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07CA220 · Schweizer G-164B

20 Jul 2007 · West Liberty, IA, United States

Schweizer G-164B · Accident: in flight collision with object during takeoff

From Walker Field (4IA2) to an unrecorded destination

Report a problem

Event

NTSB case
CHI07CA220
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

Schweizer G-164B

Aircraft type
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
N8490K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Walker Field (4IA2), West Liberty, IATo 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
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
In flight collision with object
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

  • Engine assembly › Failure
  • Object › Bird(s)

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 was substantially damaged during an emergency landing following a loss of engine power after takeoff. The pilot reported that he was taking off on runway 36 (2,300 feet by 66 feet, turf) when he encountered birds about 50 feet above ground level. He noted that the engine lost power and the aircraft settled to the ground. He was unable to stop the airplane on the remaining runway. During the runway overrun, the airplane subsequently struck a fence, encountered a ditch, and subsequently nosed over before coming to rest. A post accident survey of the runway revealed bird feathers and remains near midfield on the runway centerline.

Probable cause

The pilot's inadvertent encounter with birds immediately after takeoff and the resulting loss of engine power. Contributing factors were the fence and ditch encountered during the overrun.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07CA220
Event ID
20070803X01102
Case number
CHI07CA220
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: 7ef16c45048d5a2a786ec93f7d48fc8c16a4df92d3efd1fcce466056b22be6ca; retrieved 2026-09-21T18:26:44.896Z.