NetJets Aviation Cessna 560 Encore accident
Cessna 560 Encore · Accident: part(s) separation from aircraft en route
From Southwest Florida International Airport (KRSW) to Chicago Midway International Airport (KMDW)
Event
- NTSB case
- CEN14LA075
- 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
- Charter & commuter
- 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
Cessna 560 Encore
- Aircraft type
- Cessna 560
- 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
- N810QS
- Operator
- NetJets Aviation
- Onboard fatalities
- Unknown
- Route
- From Southwest Florida International Airport (KRSW), Fort Myers, FLTo Chicago Midway International Airport (KMDW), Chicago, IL
- Aircraft age
- About 11 years (built 2002)
- 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 135: Air Taxi & Commuter
- 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
- En route · descent
- 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
- Part(s) separation from aircraft
- 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 structures
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight crew of the twin-engine jet heard a "bang," and experienced a slight yawing of the airplane during the initial descent for landing. The flight continued to a normal landing, and a post-flight inspection revealed that the right engine upper and lower cowlings had separated from the engine and struck the right horizontal stabilizer. Recovered sections of the departed cowling doors were examined, but the reason for the separation could not be determined because the engine cowling quick-release fasteners were not recovered.
Probable cause
The inflight separation of the upper and lower right engine cowlings for reasons that could not be determined based on available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA075
- Event ID
- 20131204X10556
- Case number
- CEN14LA075
- 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: e3a6b13c52951635d128df1c52a79b50cf8e889007691024509497f336e853f6; retrieved 2026-09-15T23:09:39.561Z.