NYC08CA128 · Piper PA 32-300
Piper PA 32-300 · Accident: collision with terrain/object (non-CFIT) on approach
From Bartow Executive Airport (BOW) to Orlando Apopka Airport (X04)
Event
- NTSB case
- NYC08CA128
- 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
Piper PA 32-300
- Aircraft type
- Piper PA-32
- 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
- N812WM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bartow Executive Airport (BOW), Bartow, FLTo Orlando Apopka Airport (X04), Apopka, FL
- 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)
- 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
According to the pilot of the Piper PA 32-300, the purpose of the flight was to deliver the airplane to the new owner. While on the final leg of the approach, "everything was normal and the approach was stable." As the airplane approached the runway he saw yellow water filled barrels, depicting the displaced threshold. Assuming he would clear the barrels, he began to focus on the runway, failing to maintain an adequate flight path and clearance with the barrels. As a result, the left main geared struck one of the barrels and "sheared it off," causing substantial damage to the left wing and left horizontal stabilizer. The pilot did not report any mechanical malfunctions with the airplane prior to impact.
Probable cause
The pilot's failure to maintain clearance/altitude while on the final leg of the approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA128
- Event ID
- 20080416X00489
- Case number
- NYC08CA128
- 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, 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: d38816ef5f8712d44d74be6c512fc6fc0323eb6537d80ce8c64982c94be2f2bb; retrieved 2026-09-15T09:32:31.701Z.