Quad City CHALLENGER II accident near Amos, Ca, August 9, 2016
On August 9, 2016 at about 3:30 pm local time, a 2009 Quad City CHALLENGER II, registered CIIJW, was destroyed in an accident during takeoff near Amos. 1 person was killed.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 9, 2016 · about 3:30 pm local time · cases in 2016
- Place
- Amos, Canada
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- not recorded
- Aircraft
- Quad City CHALLENGER II II, built 2009 · all CHALLENGER IIs on the register
- Registration
- CIIJW · registered outside the United States · serial CH2-0903-2368
- Damage
- Destroyed
- Flight
- Flight
The NTSB's narrative preliminary · quoted from the NTSB record
On August 9, 2016, at 1530 UTC, a Quad City Challenger II (S/N CH2-0903-2368), C-IIJW, impacted terrain near the runway end at Amos/Magny Airport (CYEY), Amos, Quebec, Canada. The aircraft was destroyed and sole occupant on board was fatally injured. The aircraft was enroute to La Sarre Airport (CSR8), La Sarre, Quebec, Canada. This investigation is under the jurisdiction and control of the Transportation Safety Board of Canada (TSB Canada). Under the provisions of Annex 13 of the Convention on International Civil Aviation as a State of Design, the United States has designated an accredited representative to participate in the investigation. Any further information may be obtained from: TSB Canada Place du Centre 200 Promenade du Portage 4th Floor Gatineau, Quebec Canada K1A 1K8 Telephone: (8190 994-3741 Fax: (819) 953-9586 E-mail: [email protected] Investigator-in-Charge Ms. Isabelle Langevin Telephone: (514) 633-2948 E-mail: [email protected] This report is for informational purposes only and contains only information released by, or obtained from, the TSB Canada.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during takeoff defining event
The aircraft
- Maximum gross weight: 1,058 lb
- Landing gear: fixed
- Engine:; 0 hours total
- Not recorded
Weather at the time
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- Quad City CHALLENGER II 12 registered today · the model family and its accident history
- Quad City 19 aircraft on the register
- Engine: · as the NTSB recorded it
The whole map of how records connect · these connections as data: /graph/accident/CEN16WA340.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.