CHI08CA261 · Ntbk Wag Aero Sport
Ntbk Wag Aero Sport · Accident: collision with terrain/object (non-CFIT) on approach
From Green Castle Airport (IA24) to Green Castle Airport (IA24)
Event
- NTSB case
- CHI08CA261
- 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
Ntbk Wag Aero Sport
- Aircraft type
- Ntbk WAG AERO SPORT
- 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
- N141ST
- Operator
- James H. Beeghly · private individual
- Onboard fatalities
- Unknown
- Route
- From Green Castle Airport (IA24), Oxford, IATo Green Castle Airport (IA24), Oxford, IA
- 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
- Approach · VFR pattern final
- 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
- Collision with terrain/object (non-CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the total runway length is 4,800 feet, the northern 1,400 feet of which is grass and the southern 2,400 feet is asphalt. He reported that he was practicing touch and go landings on the grass portion of the runway when the accident occurred. The pilot reported that he made three touch and go landings, and decided to make one more before it got too dark. He stated that the final approach descent path appeared to be above the low-lying trees. He stated that he did not realize he was too low until he felt a "sharp blow" to the airplane and the airplane rotated to the right descending to the ground. The pilot reported that he should have realized that "...landing as close to the trees as I intended was unsafe" when the runway lights came on while he was on final approach.
Probable cause
The pilot misjudged his approach path which resulted in insufficient altitude and the subsequent failure to maintain clearance with the trees. Contributing to the accident were the trees and the dusk lighting conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA261
- Event ID
- 20080919X01502
- Case number
- CHI08CA261
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2008-08-21.
- API snapshot SHA-256: 325f78d2c9774b5b9a965c12b4514153829e1c0569639422024563087f284112; retrieved 2026-09-15T10:15:08.054Z.