FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA383 · Quad City CHALLENGER II

16 Sept 2025 · Crystal Mountain, MI, United States

Quad City CHALLENGER II · Accident: loss of control in flight during takeoff

Report a problem

Event

NTSB case
CEN25LA383
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
0
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

Quad City CHALLENGER II

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
N65176
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 34 years (built 1991)
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
Takeoff
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
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

The pilot was performing a pre-buy flight in the amateur-built airplane. The takeoff roll was normal until the airplane accelerated between 25 to 50 mph, when the airplane required right rudder to maintain straight flight. After liftoff, without pilot input, the airplane veered left of the runway. The pilot applied right rudder and was able to get the airplane back over the runway. However, he lost control of the airplane as it turned to the left despite the application of full right rudder. The airplane continued to the left until it impacted terrain. The pilot reported having completed a preflight inspection and high-speed taxi prior to the flight, and he did not note any problems. He reported that after the taxi, the owner placed a flight manual into the airplane that he thought may have jammed the rudder. Postaccident examination did not locate a flight manual in the wreckage or surrounding area, and the owner stated that a firefighter had retrieved the manual but didn’t know where in the wreckage that the firefighter had retrieved it. The pilot later thought the vertical stabilizer had more play than expected but reported that the owner told him it was normal. A postimpact examination did not reveal any anomalies in the airplane’s aileron and elevator controls, and damage to the vertical stabilizer precluded a thorough inspection of the rudder system. The airplane’s trim tabs were not installed and were not required to be. The owner had only flown the airplane once in July 2025 and reported that the airplane required constant right rudder to maintain straight flight. The owner reported informing the pilot that the airplane required right rudder. The pilot reported that he was not informed that the airplane needed right rudder and that the trim tabs were not installed. According to the kit manufacturer, extra rudder input would be required when climbing the airplane with a high angle attack and high-power setting. The pilot had logged 22 hours in a different Challenger II in September 2024. In an article published by the Experimental Aircraft Association (EAA), Before You Fly: Thoughts on your first flight and the EAA Flight Advisor Program, they advise pilots that the “Statistics show that 20% of all homebuilt accidents happen during the first two flights and are usually caused by pilot error. Those pilot errors are almost always the result of a pilot flying an aircraft for which he or she wasn't qualified or with which he wasn't familiar. The same problem exists during the first flight of any unfamiliar aircraft, whether it is a homebuilt, vintage or ultralight. The first flight in an airplane might as well be a test flight because, for that pilot, it is a test flight.”

Probable cause

The pilot’s failure to maintain aircraft control during initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA383
Event ID
20250917201025
Case number
CEN25LA383
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, cause areas. 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: c9bb0975e6d6898f62d901c25e629e4dd54f98050a56d542f983966605e4a11f; retrieved 2026-09-16T20:21:12.821Z.