Crash of a McDonnell Douglas MD-83 off Anacapa Island: 88 killed

Date & Time: Jan 31, 2000 at 1620 LT
Type of aircraft:
Operator:
Registration:
N963AS
Flight Phase:
Survivors:
No
Schedule:
Puerto Vallarta - San Francisco - Seattle - Anchorage
MSN:
53077
YOM:
1992
Flight number:
AS261
Crew on board:
5
Crew fatalities:
Pax on board:
83
Pax fatalities:
Other fatalities:
Total fatalities:
88
Captain / Total flying hours:
10460
Captain / Total hours on type:
4150.00
Copilot / Total flying hours:
8140
Copilot / Total hours on type:
8060
Aircraft flight hours:
26584
Aircraft flight cycles:
14315
Circumstances:
On January 31, 2000, about 1621 Pacific standard time, Alaska Airlines, Inc., flight 261, a McDonnell Douglas MD-83, N963AS, crashed into the Pacific Ocean about 2.7 miles north of Anacapa Island, California. The 2 pilots, 3 cabin crewmembers, and 83 passengers on board were killed, and the airplane was destroyed by impact forces. Flight 261 was operating as a scheduled international passenger flight under the provisions of 14 Code of Federal Regulations Part 121 from Lic Gustavo Diaz Ordaz International Airport, Puerto Vallarta, Mexico, to Seattle-Tacoma International Airport, Seattle, Washington, with an intermediate stop planned at San Francisco International Airport, San Francisco, California. Visual meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan.
Probable cause:
A loss of airplane pitch control resulting from the in-flight failure of the horizontal stabilizer trim system jackscrew assembly's acme nut threads. The thread failure was caused by excessive wear resulting from Alaska Airlines' insufficient lubrication of the jackscrew assembly. Contributing to the accident were Alaska Airlines' extended lubrication interval and the Federal Aviation Administration's (FAA) approval of that extension, which increased the likelihood that a missed or inadequate lubrication would result in excessive wear of the acme nut threads, and Alaska Airlines' extended end play check interval and the FAA's approval of that extension, which allowed the excessive wear of the acme nut threads to progress to failure without the opportunity for detection. Also contributing to the accident was the absence on the McDonnell Douglas MD-80 of a fail-safe mechanism to prevent the catastrophic effects of total acme nut thread loss.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 600) off Avalon: 1 killed

Date & Time: Nov 21, 1999 at 1015 LT
Registration:
N97CC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Fullerton - Fullerton
MSN:
60-0154-068
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1710
Captain / Total hours on type:
951.00
Aircraft flight hours:
4199
Circumstances:
The pilot/owner was performing a post maintenance check flight about 20 miles off shore. He was receiving visual flight advisories from a terminal radar approach facility while in level flight about 4,900 feet msl. Subsequently, the airplane started slowing then descending in a right spiral, and radar contact was lost about 1,000 feet msl. The pilot's body was recovered from the ocean. According to the autopsy report, the pilot had experienced sudden cardiac death secondary to an acute myocardial infarction due to atherosclerotic coronary artery disease. Tramadol, a painkiller not approved by the FAA for flight, was detected in a drug screen and may have masked the chest pain.
Probable cause:
The pilot's in-flight loss of control due to physical incapacitation from sudden cardiac death secondary to an acute myocardial infarction.
Final Report:

Crash of a Cessna 421C Golden Eagle III in Santa Monica

Date & Time: Sep 23, 1999 at 0703 LT
Registration:
N26585
Survivors:
Yes
Schedule:
Long Beach – Santa Monica
MSN:
421C-0832
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4050
Captain / Total hours on type:
2150.00
Aircraft flight hours:
3915
Circumstances:
During the final approach, while executing a VOR-A instrument approach, the airplane landed hard, collided with the runway VASI display, and caught fire. The airplane had received radar vectors for the approach and was turned to a 20-degree intercept for the final approach course when 2.5 miles from the initial approach fix. Radar track data showed the airplane continued inbound to the field slightly left of course with a ground speed varying between 135 and 125 knots and a descent rate of approximately 700 feet per minute. The pilot said he descended through the clouds about 850 feet above ground level and saw the airport approximately 1 to 2 miles ahead. He noticed that he was left of the runway centerline and corrected to the right. He realized that he had overcorrected and turned back to the left. The pilot reported that he felt that the approach was stabilized although the descent rate was greater than usual. The airplane impacted the ground about 1,000 feet from the approach end of the runway abeam the air traffic control tower on an approximate heading of 185 degrees. The impact collapsed the landing gear and the airplane slid forward another 1,000 feet down the runway and came to rest approximately midfield on the runway. The pilot stated that he had not experienced any mechanical problems with the aircraft or the navigation equipment prior to the accident. A Special Weather Observation taken at the time of the accident contained the following: sky condition overcast at 500 feet; winds from 230 degrees at 3 knots; visibility 2 miles.
Probable cause:
The failure of the pilot to establish and maintain a stabilized approach, which resulted in a hard landing and on-ground collision with the airport VASI display.
Final Report: