CHI03LA236 · Polsgrove Bluegrass Express
Polsgrove Bluegrass Express · Accident: in flight collision with terrain/water
From Georgetown-Scott County Regional Airport (27K) to Charles B. Wheeler Downtown Airport (MKC)
Event
- NTSB case
- CHI03LA236
- 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
- 1 · 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
Polsgrove Bluegrass Express
- Aircraft type
- Polsgrove BLUEGRASS EXPRESS
- 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
- N113YE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Georgetown-Scott County Regional Airport (27K), Georgetown, KYTo Charles B. Wheeler Downtown Airport (MKC), Kansas City, MO
- 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
- Unknown
- 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 terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The experimental amateur homebuilt airplane was destroyed on impact with terrain. The pilot was fatally injured. A witness said that the pilot said he was leaving for Kansas City ,Missouri . Another witness said that the accident flight's takeoff was approximately 1130 on January 9, 2003. On January 25, 2003, a missing persons report was filed. The airplane's route of flight was searched by air and ground teams. The searching did not find the wreckage and on February 19, 2003, the mission was suspended. On July 30, 2003, the wreckage was found. Weather along a direct route of flight was VFR. Due to the damage the airplane sustained, pre-impact anomalies were unable to be determined. Decomposition of the body precluded a Final Forensic Toxicology Accident Report. The accident site was along a direct route of flight. The Civil Air Patrol Incident Commander stated that their search was hampered because of the time lapse between his departure and the report that he was overdue.
Probable cause
Undetermined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA236
- Event ID
- 20030812X01314
- Case number
- CHI03LA236
- 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: 4f07000cbecadd094fe2347444bdf672553db13b5a10a4be85d6fda346ae5f41; retrieved 2026-09-20T19:31:46.582Z.