FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA326 · Aeropro CZ Eurofox

30 May 2009 · Bloomfield, IN, United States

Aeropro CZ Eurofox · Accident: nose over/nose down during landing

From Bowling Green Warren County Regional Airport (BWG) to Shawnee Field (1I3)

Report a problem

Event

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

Aeropro CZ Eurofox

Aircraft type
Aeropro CZ EUROFOX
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
N817R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bowling Green Warren County Regional Airport (BWG), Bowling Green, KYTo Shawnee Field (1I3), Bloomfield, IN
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 91: General Aviation
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
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
Nose over/nose down
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A sport pilot and a student sport pilot departed on a cross-country personal flight to the destination airport. The sport pilot was the flying pilot and the student pilot assumed navigational duties during the flight. They had been using a global positioning system receiver for the flight. When they arrived at the destination airport, the sport pilot twice overflew the runway. There had been a discussion between the pilots regarding the location of the runway. The sport pilot then established an approach to a recently plowed agricultural field located about 250 yards west of the runway and landed on that field. During the landing the nose gear dug into the soft soil and the airplane nosed over. Both wings were bent downward approximately 10 degrees, the pilot compartment frame was bent and the windscreen was broken.

Probable cause

The pilot's selection of an unsuitable landing area.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA326
Event ID
20090601X51646
Case number
CEN09CA326
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: 4efdc885a01cc2794089e8a073fcc79fc126f1ff72148ea79d782a99c278ed9c; retrieved 2026-09-15T11:15:21.928Z.