This earlier photograph shows the aircraft's rear engines and tail arrangement. The stabilizer jackscrew assembly central to the Flight 261 investigation is inside the tail and cannot be inspected in this photograph.
Resized and JPEG recompressed; no content changes.
Geographic context
Puerto Vallarta
San Francisco (planned stop)
Seattle (planned destination)
Los Angeles (intended diversion)
Anacapa Island reference
Approximate airport and geographical reference positions. This schematic shows the planned journey and relevant locations, not a recorded flight track. Basemap: Natural Earth, public domain.Read supporting evidence
Flight 261 developed a jammed horizontal stabilizer trim system during its climb. The crew maintained flight with sustained control-column force, consulted company personnel and planned to divert to Los Angeles. The stabilizer then moved sharply nose down, causing an initial dive from which the crew temporarily recovered. A second upset became an unrecoverable loss of pitch control. The aircraft struck the Pacific Ocean, killing all 88 occupants.
Read the full incident Follow what happened, from the flight to the investigation findings.
What investigators concluded
The NTSB attributed the loss of pitch control to failure of the jackscrew assembly's acme nut threads. Excessive wear resulted from insufficient lubrication. Extended lubrication and end-play inspection intervals, approved by the FAA, allowed inadequate lubrication and wear to progress without timely detection. The absence of a fail-safe mechanism to prevent catastrophe after complete thread loss was also a contributing factor.
A jammed stabilizer and the loss of Alaska flight 261
1,720 words / about 8 minutes to read. Based on the investigation records cited below.
The trim system stops during the climb
Alaska Airlines flight 261 left Puerto Vallarta, Mexico, on January 31, 2000, bound for San Francisco and then Seattle. The McDonnell Douglas MD-83, registered N963AS, carried 83 passengers and five crewmembers. Three of the passengers were young children travelling on laps. The aircraft departed at about 13:37 Pacific Standard Time. The first officer was initially flying, and the planned cruise altitude was 31,000 feet. The weather was suitable for visual observation and was not found to have caused the accident.
During the early climb, the horizontal stabilizer moved normally to trim the aircraft. Trim adjusts the tail's position so that the pilots do not have to hold a continuous force on their control columns to maintain the required pitch. At about 23,400 feet, the stabilizer stopped moving. The last recorded movement before the later dive was at 13:49:51. The aircraft continued climbing, but the tail position no longer responded normally to autopilot or pilot commands.
The autopilot disengaged as the aircraft passed roughly 28,557 feet. For the next several minutes, the aircraft climbed slowly while substantial pulling force was applied to the controls. At cruise altitude, the required force varied with speed, but the aircraft remained flyable. This was the beginning of a prolonged emergency involving a jammed stabilizer, rather than an immediate loss of all control. The pilots could hold a flight condition for a time, while the mechanical fault within the trim assembly remained unresolved.
The crew contacted company dispatch and maintenance personnel to discuss the jammed stabilizer and a possible diversion to Los Angeles. The cockpit voice recording covers the last part of those conversations, rather than the entire flight from departure. By then, the pilots had spent a considerable period managing the aircraft with the stabilizer fixed. They considered the landing conditions at San Francisco and Los Angeles, including winds, runway conditions and the effect on ground speed.
The captain preferred Los Angeles as a suitable place to land the damaged aircraft. Dispatch supplied weather information and also discussed traffic delays that might follow a diversion. The final report found that dispatch personnel appeared to have tried to influence the crew to continue to San Francisco. It nevertheless assessed the captain's decision to divert to Los Angeles as prudent and appropriate. The exchanges are evidence of operational discussion under an emergency, rather than proof that schedule considerations caused the mechanical failure.
Maintenance personnel asked which trim controls the pilots had tried. The captain reported attempts with both the normal control-wheel switches and the pedestal handles, and said that the alternate system also appeared jammed. An electrical load indication suggested that the primary trim motor was trying to operate without moving the assembly. That observation did not reveal the internal condition of the jackscrew and nut. The pilots and the maintenance staff recognized a malfunction but could not determine its mechanical cause from the cockpit indications and radio exchanges available to them.
At about 16:09:16, the autopilot disconnected and the stabilizer suddenly moved farther in the nose-down direction. The aircraft began an approximately 80-second dive from about 31,050 feet to between 23,000 and 24,000 feet. The crew reported the loss of vertical control to air traffic control. The speed increased substantially, and the recorder captured an overspeed warning. This was a marked deterioration from the earlier condition in which the stabilizer was jammed but the aircraft could be held in level flight.
The pilots applied strong nose-up control inputs, and speedbrakes were deployed during the descent. Performance calculations indicated combined pulling forces of roughly 130 to 140 pounds during recovery. Those figures refer to the combined force on the two control columns. The report does not establish how much either pilot individually applied. Assigning the whole calculated load to one person would give a misleading description of the evidence.
The descent was arrested near 24,000 feet, and air traffic control provided a block altitude in which the aircraft could maneuver. Although the aircraft had recovered from the immediate dive, normal trim operation had not returned. The captain reported that it still wanted to pitch down, and further strong control forces were needed to maintain its condition. Recovery therefore meant regaining a temporary manageable flight path. It did not mean that the damaged assembly was repaired, that its load-bearing parts were secure or that an ordinary approach to Los Angeles could now be assumed.
After the first dive, the pilots discussed the risk of trying the trim controls again. The first officer cautioned against repeating the earlier action, and the captain told maintenance that the situation had become worse. Around this time, calculations indicated combined pulling forces of about 120 pounds. The aircraft was maintaining altitude with difficulty while the crew considered how to descend and configure it for a landing.
The captain asked to make configuration changes over the sea so that he could assess whether the aircraft remained controllable before approaching Los Angeles. Air traffic control cleared a descent to 17,000 feet. The last transmitted radio message from flight 261 was at about 16:17:02. The captain then directed the cabin crew to secure the cabin and ensure that passengers were restrained. The continuing work was now aimed at preparing a badly compromised aircraft for a possible landing, with uncertainty about how it would respond.
The crew extended slats and selected 11 degrees of flap, then retracted them. They also discussed unloading the aircraft and whether further trim operation was appropriate. The first officer suggested trying to land while the aircraft was still controllable, and the captain agreed to head for Los Angeles. The report later criticized aspects of the troubleshooting and autopilot use, while also finding that the available guidance was insufficiently clear about appropriate actions for malfunctioning flight controls. This period should be described through the recorded actions and findings, without inventing an assurance that the crew understood the failure inside the tail.
At about 16:19:36.6, the voice recorder captured a very loud noise and increasing background sound. The flight data showed a rapid nose-down pitch movement, negative acceleration and a developing roll to the left. Within seconds the aircraft reached a recorded pitch angle of about 70 degrees nose down. It then rolled to an inverted attitude. The crew continued making control inputs as the aircraft descended, but the changes did not produce a recoverable flight condition.
The aircraft remained near inverted through much of the final recorded sequence, with its pitch continuing to vary nose down. The cockpit recordings ended at about 16:20:57. Flight 261 struck the Pacific near Port Hueneme, about 2.7 miles north of Anacapa Island. All 88 occupants died. The aircraft was destroyed. Wreckage recovered from the ocean later allowed investigators to examine the tail mechanism that the crew had been unable to inspect or repair in flight.
The NTSB found that the final dive followed a low-cycle fatigue fracture of the torque tube and failure of brackets in the vertical stabilizer tip fairing. These failures allowed the horizontal stabilizer's leading edge to move much farther upward than a functioning jackscrew assembly permitted. That tail movement produced an overwhelming nose-down pitching effect. The board concluded that recovery from this final condition was not possible. The aircraft's inverted attitude belongs to that uncontrollable descent; it should not be described as a stable technique that restored a safe way to fly the damaged aircraft.
The stabilizer trim mechanism depended on a threaded screw working inside an acme nut. The nut's threads had worn excessively and were stripped during the accident flight. The assembly initially jammed as the aircraft climbed through about 23,400 feet. Investigators could establish that jam, but could not determine its exact physical cause. They considered several possible interactions involving worn threads, their remnants and the loads on the screw. That remaining uncertainty does not mean the later loss of the threads was merely hypothetical.
During the first dive, the jam released and aerodynamic loads pulled the screw upward through the stripped nut. A lower mechanical stop temporarily prevented it from separating completely. That explains why the first dive could be arrested while the assembly remained critically damaged. The final failure removed the remaining restraint and permitted the much larger stabilizer movement that produced the fatal descent. The sequence involved progressive loss of mechanical support, rather than a single electrical command continuously driving an intact trim mechanism.
Examination found no effective lubrication on the working interface of the screw and nut. Investigators checked whether seawater immersion and recovery procedures could account for the absence of grease. Laboratory work and evidence from other greased components supported the finding of inadequate lubrication before the crash. They also examined maintenance practices and the condition of grease passages. The conclusion was based on several types of evidence, not simply an assumption that a component brought up from the ocean must look exactly as it had before impact.
The NTSB's adopted probable cause was the loss of pitch control following failure of the jackscrew assembly's acme nut threads. It attributed the excessive wear to insufficient lubrication by Alaska Airlines. The report also identified extended lubrication intervals, and FAA approval of those extensions, as contributing factors. Longer intervals increased the consequences of a missed or inadequately performed lubrication task. The physical wear was therefore examined alongside the maintenance system intended to prevent it.
A separate inspection task measured end play to monitor wear between the screw and nut. The report found that extended end-play check intervals, also approved by the FAA, allowed wear to progress without another opportunity for detection before failure. It further identified the absence of a fail-safe mechanism that would prevent complete thread loss from becoming catastrophic. Lubrication, detection and design protection were different safeguards, and the report found deficiencies across them. Its conclusions also described wider problems in Alaska's maintenance program and inadequate regulatory oversight.
The board did not find weather, bird impact or a separate initial engine failure responsible for the accident. Both engines were operating normally before the final dive. Its recommendations addressed maintenance intervals, inspection procedures, oversight and protection against catastrophic trim-system failures. Those are investigation-era proposals and findings, not a statement that every recommendation has since been implemented. The failure progressed from a jammed but temporarily manageable stabilizer to a loss of restraint from which recovery was impossible. The investigation traced it back to maintenance and design safeguards.
The report identifies this as the final recorded stabilizer movement before the first dive, about two hours and 20 minutes later. The crew subsequently flew with sustained pulling force.
Autopilot disconnection was followed by stabilizer movement to 2.5 degrees nose down. The aircraft descended from about 31,050 feet to between 23,000 and 24,000 feet over roughly 80 seconds.
The aircraft was maintaining about 24,400 feet at 262 knots. Performance calculations indicated large combined pulling forces were needed to recover from the dive.
16:19:36.6 to about 16:21Final upset and ocean impact
A loud noise and sharp nose-down motion marked the second upset. The aircraft rolled inverted. The flight recording ended at 16:20:56.3 and impact followed near Anacapa Island.
Why was the aircraft still flying after the trim system jammed?
The crew maintained flight using sustained pulling force. Later recovery from the first dive required large combined pulling forces; continued flight did not mean the trim system was functioning.
Did the investigation focus only on maintenance staff?
No. It also identified extended maintenance intervals, FAA approval of those intervals, and the lack of fail-safe design protection as contributing factors.
The crew recovered from one dive. That temporary recovery should not be interpreted as evidence that the underlying mechanical failure had been corrected.
A contributing factor is not a complete explanation
The probable-cause finding includes maintenance, oversight and design protection. Selecting just one of these loses the investigation's wider conclusion.
Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.
Recommended: limit troubleshooting and land
Recommendation A-02-36 called for checklist-only responses to malfunctioning flight controls and landing at the nearest suitable airport when checklist procedures were ineffective. This is the recommendation recorded in the 2002 report, not a claim of present implementation.
Recommended: maintenance margins and fail-safe design
A-02-41 and A-02-42 called for review of critical maintenance intervals, supporting technical analysis and appropriate safety margins. A-02-49 called for review of fail-safe protection and catastrophic single-point failures. Present implementation status has not been independently established here.
Matching dossiers for Absence of fail-safe protection: No other dossier in this collection.
Read alongside
These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.
Both investigations examine how a critical mechanical failure overwhelmed flight-control protection. United 232 lost hydraulic control after an engine disc failure; Alaska 261 lost stabilizer restraint after jackscrew thread wear.
Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.
Official case overview and links to the investigation record and recommendations.
Sources and transparency
Checked against the NTSB final report through source and page comparison. No independent expert review.
Source limitations
Chronology describes recorded events; the probable-cause conclusion separately attributes the underlying mechanical failure. The temporary recovery did not restore a functioning trim system. Crew dialogue, report photographs and diagrams are not reproduced.
Loss of Control and Impact with Pacific Ocean, Alaska Airlines Flight 261, McDonnell Douglas MD-83, N963AS, January 31, 2000
National Transportation Safety Board NTSB/AAR-02/01, adopted 10 December 2002
Brief attributed excerpts for source-based commentary. Full report, photographs and third-party material are not republished. Source terms / provenance.
Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.
Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed
Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.
Revision history
: Checked report citations and source hashes. Added credited photographs, geographic context, sequence diagrams, reader answers, evidence limits, report-era safety follow-up, further records, sourced incident comparisons and this editorial record.
: Added a full chronological account with section-level report references and links from the short summary.
