CEN17FA053 · Aircraft MFG & Design LLC CH601XL SLSA
Aircraft MFG & Design LLC CH601XL SLSA · Accident: loss of control in flight en route
From Poplar Grove Airport (C77) to Schaumburg Regional Airport (06C)
Event
- NTSB case
- CEN17FA053
- 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
Aircraft MFG & Design LLC CH601XL SLSA
- Aircraft type
- Aircraft MFG Design CH601
- 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
- N4218
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Poplar Grove Airport (C77), Poplar Grove, ILTo Schaumburg Regional Airport (06C), Schaumburg, IL
- Aircraft age
- About 8 years (built 2008)
- 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
- En route · cruise
- 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
- Loss of control in flight
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The light sport pilot decided to conduct a night cross-country flight in his light sport airplane even though he was not current to act as pilot-in-command at night. Radar data depicted the airplane departing after sunset and proceeding along the intended route of flight. The last radar contact was at 3,500 ft above mean sea level (msl), about 2,600 ft above ground level, about 0.5 mile from the accident site. There were no witnesses to the accident, and the wreckage was located the following morning in a plowed field along the intended route of flight about 12.6 nautical miles from the departure airport.
The impact damage to the airframe was consistent with the airplane impacting the terrain while inverted. A postaccident examination of the airframe and engine did not reveal any anomalies consistent with a preimpact failure or malfunction.
The pilot's sport pilot certificate did not authorize him to fly at night. In conjunction with his private pilot training, he had an expired 90-day endorsement for night flight that was dated about 14 months before the accident. It is possible that the pilot became spatially disoriented and lost control of the airplane; however, given that the pilot had been flying at night and that there were no mechanical anomalies identified during the investigation, the reason for the loss of control could not be determined.
Probable cause
A loss of control in flight for reasons that could not be determined because no anomalies consistent with a preimpact failure or malfunction were identified during the investigation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17FA053
- Event ID
- 20161210X01354
- Case number
- CEN17FA053
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-12-10.
- API snapshot SHA-256: 3ca6f4aca291b95fb0ddc9cacd1011dee426acc00a8d21054ad3c7c1ea81ab30; retrieved 2026-09-14T22:03:48.577Z.