SEA03FA147 · Cessna Citation 525
Cessna Citation 525 · Accident: airframe, component or system failure en route
From Victoria International Airport (CYYJ) to Boise Air Terminal/Gowen Field (BOI)
Event
- NTSB case
- SEA03FA147
- 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
- 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
Cessna Citation 525
- Aircraft type
- Cessna CITATION 525
- 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
- N996JR
- Operator
- James C. Ray · private individual
- Onboard fatalities
- Unknown
- Route
- From Victoria International Airport (CYYJ), SidneyTo Boise Air Terminal/Gowen Field (BOI), Boise, ID
- Aircraft age
- Not recorded
- 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 · climb to cruise
- First occurrenceThe 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
- Airframe, component or system 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
- Electrical system, electric motor › Activated
- Electrical system, electric relay › Failure
- Flt control syst, elevator trim/tab control › Uncommanded
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The corporate jet airplane experienced a loss of elevator trim control (runaway trim) that resulted in an uncommanded nose-low pitch attitude. The pilot reported that following the loss of elevator trim authority the airplane was extremely difficult to control and the elevator control forces were extremely high. The pilot continued to maneuver the airplane, but eventually ditched it into a nearby marine cove. The runaway trim condition was not immediately recognized by the pilot and he stated that, by that point in the event sequence, the control forces were so great that he had little time to troubleshoot the system and elected to continue on his established heading and ditch the airplane. Pulling the circuit breaker, which is called for by the checklist in the event of a trim runaway, would have arrested the trim movement. Post accident examination and functional testing of the airplane's electric pitch trim printed circuit board (PCB) showed a repeatable fault in the operation of the PCB's K6 relay, resulting in the relay contacts remaining closed. This condition would be representative of the autopilot pitch trim remaining engaged, providing an electrical current to drive continuous nose-down trim to the elevator trim motor. Examination of the airplane's maintenance records showed that the PCB was removed and replaced in conjunction with the phase inspection prior to the accident. Further examination of the airplane's maintenance records revealed that the replacement PCB was originally installed in an airplane that experienced an "electric trim runaway on the ground." Following the trim runaway, the PCB was removed and shipped to the manufacturer. After receiving the PCB the manufacturer tested the board and no discrepancies were noted. The unit was subsequently approved for return to service and later installed on the accident airplane. The investigation revealed a single-point failure of trim runaway (failed K6 relay) and a latent system design anomaly in the autopilot/trim disconnect switch on the airplane's pitch trim PCB. This design prohibited the disengagement of the electric trim motor during autopilot operation. As a result of the investigation, the FAA issued three airworthiness directives (AD 2003-21-07, AD 2003-23-20, and AD 2004-14-20), and the pitch trim printed circuit board was redesigned and evaluated for compliance with safety requirements via system safety assessment
Probable cause
The loss of airplane pitch control (trim runway and mistrim condition) resulting from a failure in the airplane's electric pitch trim system. Factors that contributed to the accident were the manufacturer's inadequate design of the pitch trim circuitry that allowed for a single-point failure mode, and the absence of an adequate failure warning system to clearly alert the pilot to the pitch trim runaway condition in sufficient time to respond in accordance with the manufacturer's checklist instructions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03FA147
- Event ID
- 20030724X01192
- Case number
- SEA03FA147
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: e77ebcb5dfb3582c085669995584b45cad99c51e92ad2d1b9ad40d8240d00003; retrieved 2026-09-22T08:55:27.491Z.