FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hawaiian Airlines Flight 197

12 Jan 2003 · Kahului, HI, United States

Boeing 717-200 · Incident en route

From Kahului International Airport (OGG) to Daniel K. Inouye International Airport (HNL)

Report a problem

Event

NTSB case
LAX03IA098
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
Incident
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
Airline
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

Boeing 717-200

Aircraft type
Boeing 717
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
N482HA
Onboard fatalities
Unknown
Route
From Kahului International Airport (OGG), Kahului, HITo Daniel K. Inouye International Airport (HNL), Honolulu, HI
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 121: Air Carrier
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
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Flightcrew › Checklist, not complied with
  • Flt control syst, aileron trim/tab control › Incorrect

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane unexpectedly rolled to the left during the climb to cruise. The takeoff and initial area departure phases were normal. The captain engaged the autopilot at 3,000 feet mean sea level (msl). Passing 8,900 feet msl, the airplane experienced a sudden upset resulting in a rapid roll of 35 degrees to the left. The captain countered with 50 to 60 degrees of right aileron input. The autopilot had been engaged, but disengaged automatically during the pilot control input. The first officer (FO) asked the captain if he wanted some aileron trim. The captain responded that he desired only a small amount, reasoning that he did not want to mask a major problem. He did not feel any vibration, binding, or unusual control feel other than the effort and aileron input required to hold wings level. He remembered seeing the right aileron and right elevator deflected upward on the Configuration synoptic page on the systems display, and thought that the aileron deflection would be consistent with his control input to lower the right wing against a left rolling tendency. He flew the airplane to a landing with approximately 45 degrees yoke deflection required to maintain a level wing attitude. Analysis of the digital flight data recorder (DFDR) data indicated that the aileron trim value was 90 percent of full aileron trim authority prior to pushback, engine start, taxi, and takeoff. The data from the previous inbound flight, which had the same flight crew showed that the trim changed from 10 to 90 percent authority about 3 minutes after the previous flight landed. The trim again shifted following the landing and taxi back of the event flight from 85 percent to 10 percent. The captain said that he felt that the airplane was not tracking properly after takeoff. The airline's debrief of the flight crew indicated that they did not see or recognize the excessive aileron deflection on the cockpit screens before or after the event worsened and resulted in autopilot disengagement. The autopilot was trying to roll out of a turn, and was commanding aileron in a direction opposite to the trim position, which resulted in the aileron torque limiter reducing the aileron authority. With the reduced authority, the aileron position could not keep up with the autopilot command, which triggered a autopilot disconnect. The airline indicated that the Rudder and Aileron check for zero is done during the Cockpit Preparation Checklist, which a crew accomplishes just prior to the Before Starting Engines Checklist. DFDR data about 2/3 of the way through the flight indicated that the trim did respond when the copilot manipulated it. The data also showed that the trim repositioned back to zero at the end of the flight. Thorough post accident tests of the system found that the aileron trim control switches and the aileron trim control actuator unit functioned per design specifications with no mechanical or circuit discrepancies noted. Testing demonstrated that there was no evidence of any uncommanded motion. Tests were also performed on the Aileron and Rudder Trim Control Module (ARTCM) and no faults were found.

Probable cause

the flight crew's failure to follow the checklist and detect an out of trim condition prior to takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03IA098
Event ID
20030325X00388
Case number
LAX03IA098
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, damage. 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: 536eb12fee453ebb418f246690492ec5ca67e96e60b9d56e5a719b914c16a24f; retrieved 2026-09-18T15:56:08.177Z.
  • The NTSB's operator name is blank for N482HA; the operator shown is the name the NTSB's other records give its FAA operator code, HALA.