ANC25LA008 · Cub Crafters Inc CC18-180
National Park Service Cub Crafters Inc CC18-180 · Accident: flight control system malfunction/failure during takeoff
From an unrecorded airport to Fairbanks International Airport (FAI)
Event
- NTSB case
- ANC25LA008
- 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
- Government
- 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
Cub Crafters Inc CC18-180
- Aircraft type
- Cub Crafters CC18
- 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
- N55PK
- Operator
- National Park Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Fairbanks International Airport (FAI), Fairbanks, AK
- Aircraft age
- About 5 years (built 2019)
- 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
- Public Aircraft
- 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
- Flight control system malfunction/failure
- 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 systems
- Personnel issues › Experience/knowledge
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 reported that during takeoff, just after becoming airborne, he was unable to move the flight control stick forward. The airplane started climbing aggressively and the pilot attempted to recover using elevator trim control. The airplane subsequently stalled and began an uncontrolled, nose-down descent toward the runway. During the descent, the pilot was able to level the airplane; however, there was insufficient altitude to recover from the stall. The airplane impacted the runway, resulting in substantial damage to the fuselage and both wing lift struts. The accident pilot reported that just before departure, he did a control system check, which did not reveal any anomalies. A postaccident examination revealed that the rear flight control stick was incorrectly installed. The flight control stick was installed in reverse. The curve of the control stick was curved forward, which resulted in the control stick contacting the pilot’s (front) seatback, which limited movement and prevented the control stick from moving full forward. The investigation did not determine who improperly installed the control stick. However, it was normal practice for the pilots to remove and reinstall the rear seat control stick if they were flying with just cargo in the rear seat area. The pilot reported that he has never removed the control stick and was not trained to do so. Had the pilot been trained on the removal and installation of the control stick, he may have noticed the control stick was installed backwards during his preflight. He also stated that he was not aware that the control stick could be installed incorrectly. The airplane manufacturers’ supplement dated January 13, 2016, which describes the process and requirements for reinstalling the rear control stick, states in part: “Ensure full range of motion (including trim) is met without the rear stick contacting anything.” Additionally, the supplement must be added to the pilot’s operating handbook and the Federal Aviation Administration approved flight manual when the rear control stick is removed and reinstalled. Following the accident, the operator issued an agency safety alert to address the correct installation of the rear flight control stick. Additionally, the safety alert highlights the preflight and before takeoff checklists requiring flight control checks to verify the maximum range of travel.
Probable cause
The incorrect installation of the rear flight control stick, resulting in the pilot’s inability to control the pitch attitude, coupled with the pilot’s inadequate control system check before departure, all which resulted in an aerodynamic stall during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC25LA008
- Event ID
- 20241103195428
- Case number
- ANC25LA008
- 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: cc44cefdde5e268cc1aebea62ace0f3fca812ada011b70024388234f5bafe938; retrieved 2026-09-16T19:26:31.373Z.