alaska aviation accident data: Case Analysis - Database

alaska aviation accident data: Case Analysis

Detailed breakdown of Alaska 261 accident data, mechanical failures, and maintenance factors.

2026-07-25
aviation accident vs incident Wiki Team
Quick Guide
  • Alaska 261: Critical data on stabilizer failure.
  • Jack screw: Excessive wear caused the crash.
  • Maintenance intervals: Extended checks led to oversight.
  • Pilot response: Heroic efforts to control the dive.
  • Safety impact: New regulations on inspection protocols.

Flight Data Profile

This section outlines the core data points of Alaska Airlines Flight 261, including aircraft specifications and crew experience. Understanding these baseline metrics is essential for analyzing the accident data.

Aircraft Details

  • Type: McDonnell Douglas MD-83
  • Manufactured: 1992
  • Flight Hours: ~27,000 hours
  • Cycles: ~14,000 takeoffs/landings

Crew Experience

  • Captain: Ted Thompson (18,000 hrs)
  • First Officer: William Tansky (8,000 hrs)
  • Records: Spotless safety history
  • Background: Military veterans
Data Anomaly

The aircraft had a hidden mechanical defect that standard flight data did not reveal until failure was imminent.

Mechanical Failure Analysis

The primary cause of the accident was the failure of the horizontal stabilizer trim system. The following data points explain the sequence of mechanical failures that led to the crash.

Key Failure Points:

  • Jack Screw: Excessive wear on threads.
  • Acme Nut: Stripped threads due to friction.
  • Lubrication: Insufficient maintenance over time.
  • Stabilizer: Jammed at 0.4 degrees nose down.
Technical Insight

The extended maintenance intervals, approved by the FAA, allowed the Acme nut threads to wear down beyond safe limits without detection.

Comparison of Systems:

  • Primary Trim: Electrical motor failed to move stabilizer.
  • Alternate Trim: No response to pilot input.
  • Manual Control: Required 140 lbs of force.
  • Autopilot: Disengaged due to extreme pitch forces.

Timeline of Events

The following steps reconstruct the final moments of the flight based on cockpit voice recorder and flight data recorder analysis.

1

Initial Climb

Aircraft climbs to 31,000 ft. Pilots notice stiff controls requiring 30-50 lbs of force to maintain altitude. Autopilot struggles to compensate.

2

Troubleshooting

Crew attempts to use pickle switches and suitcase handles to free the jammed stabilizer. Both primary and alternate trim systems fail to resolve the issue.

3

The Dive

At 4:00 PM, the jack screw fails completely. The stabilizer moves to full nose-down position, causing a vertical dive near 26,000 ft.

4

Recovery Attempt

Pilots exert maximum force to level the plane at 24,000 ft. They deploy speed brakes and prepare for an emergency landing in Los Angeles.

5

Final Impact

During approach preparation, the stabilizer mechanism fails catastrophically. The aircraft enters an unrecoverable inverted dive and impacts the ocean.

Critical Moment

The decision to invert the aircraft was a desperate, last-resort maneuver to counteract the nose-down pitch, proving the pilots' dedication to saving the flight.

Safety Investigation Outcomes

The investigation into the Alaska 261 data led to significant changes in aviation safety regulations. These findings transformed maintenance protocols across the industry.

Major Regulation Changes:

  • Inspection Frequency: Mandatory checks for jack screw assemblies.
  • Lubrication Standards: Strict intervals for lubricating critical parts.
  • Endoscope Checks: Required internal inspection of acme nuts.
  • Maintenance Oversight: Stricter FAA oversight of interval extensions.

NTSB Finding

  • Cause: Lack of lubrication.
  • Factor: Extended maintenance intervals.
  • Result: Total loss of pitch control.

Systemic Failure

  • Oversight: Insufficient regulatory checks.
  • Pressure: Cost-cutting measures.
  • Culture: Operational flow vs. safety.

Crew Recognition

  • Award: Gold Medal for Heroism.
  • Reason: Attempted to save passengers.
  • Impact: Prevented ground casualties.
Legacy

This accident data serves as a crucial case study for maintenance engineering and pilot training regarding runaway trim scenarios.

Essential Data Checklist

Review this checklist to ensure comprehensive understanding of the accident factors and the subsequent safety improvements.

Analysis Milestones:

  • Review maintenance history of MD-83 tail components
  • Understand the function of the jackscrew assembly
  • Analyze the crew's troubleshooting checklist actions
  • Identify the specific NTSB recommendations implemented
  • Examine the timeline of the final dive sequence
Data Access

Official reports and raw data from the investigation are available through the National Transportation Safety Board archives.

Q: What specific data indicated the jackscrew failure?

Post-recovery analysis showed the Acme nut threads were completely stripped off the jackscrew mechanism, leaving only smooth metal.

Q: Could the pilots have saved the aircraft with different actions?

Investigation concluded that once the jackscrew failed, the aircraft was structurally uncontrollable. No procedural change could have recovered the flight.

Q: How did this accident change maintenance data requirements?

It forced airlines to implement more rigorous endoscopic inspections of jackscrew assemblies and reduce the time between lubrication checks.