NTSB CAROL · Event
Event ANC03LA032
Registry · N903AK
FAA Aircraft Registry record.
Make / Model
BOEING 737-9
Year of manufacture
2023
TCDS
A16WE · THE BOEING CO
Engine
CFM INTL LEAP-1B28 SER
Seats / Engines
48 seats · 2 engines
Last airworthiness date
20230929
ADS-B equipped
Yes — Mode-S AC7A5B
Registrant of record
ALASKA AIRLINES INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The improper installation of an engine fuel line fitting by contracted maintenance personnel resulting in an in-flight engine fire. Contributing factors in the accident were an inadequate annual inspection by company maintenance personnel, and the lack of suitable terrain for a forced landing.
Factual narrative
On March 19, 2003, about 1015 Alaska standard time, a Rockwell 500-S airplane, N903AK, sustained substantial damage when it encountered rough terrain during a forced landing following an in-flight engine fire, about 2 miles east-southeast of Chickaloon, Alaska. The airplane was being operated as a visual flight rules (VFR) local area maintenance test flight under Title 14, CFR Part 91, when the accident occurred. The airplane was operated by the State of Alaska Division of Forestry, Palmer, Alaska. The airline transport certificated pilot, and the sole passenger, were not injured. Visual meteorological conditions prevailed, and VFR flight following procedures were in effect. The flight originated at the Palmer Municipal Airport, Palmer, at 0953. During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), on March 19, the pilot reported the airplane had undergone extensive maintenance, including overhauls of both engines, and installation of a turbocharger system. The engines were installed by maintenance personnel under contract with the Division of Forestry. Following installation, the engines were ground-run to assess their performance, and to check for any fluid leaks. No leaks were found. An annual inspection was then completed by maintenance personnel with the Division of Forestry, and the airplane was released for a maintenance test flight. The passenger on the test flight was the mechanic who installed the engines. The pilot reported that he performed a preflight and engine runup, and no discrepancies were noted. The takeoff, with engine power settings of 30 inches of manifold pressure and 2,700 rpm, was normal. The accident flight was intended to check the turbocharging system by climbing to 12,000 feet. One of the Division of Forestry pilots observed the takeoff from the Palmer Airport. He said he noticed what appeared to be a slight vapor trail coming from the left engine of the accident airplane. He did not report his observations to the pilot. The pilot reported that while climbing through 8,000 feet, the electrical system experienced a spike, but then returned to normal. As the airplane approached 11,000 feet, the left engine's fuel pressure began to fluctuate. The manifold pressure and rpm began to decrease. The pilot feathered the propeller, and shut-off the left engine's fuel/hydraulic valve. He informed his Division of Forestry dispatcher that the flight was returning to Palmer. The passenger then noted that flames were visible coming from the left engine. The pilot began an emergency descent toward a forced landing area. He selected a gravel bar near the Matanuska River, and landed with the landing gear and flaps extended. During the landing roll, the airplane received extensive damage to the fuselage and landing gear. When the airplane came to a stop, the pilot and passenger exited the airplane and extinguished the flames from the left engine with a hand-held fire extinguisher. The pilot reported that the left engine, the left side of the fuselage, and the underside of the wing had oil streaking. A trail of oil was visible on the ground along the airplane's approach path to its final resting point. After the airplane was recovered, it was examined on March 24 and 25, 2003, by the NTSB IIC, other NTSB personnel, and an FAA airworthiness inspector. The examination revealed fire damage, melting of skin material, and sooting along the upper and left side of the left engine nacelle adjacent to the aft edge of the wing. The inboard side of the left engine cowling was scorched and fire damaged. The left inboard flap had scorching and destruction of the upper surface. Oil smudging and streaking were found along the underside of the left engine cowling, the left side of the fuselage, the underside of the inboard portion of the left wing, and the underside of the left horizontal stabilizer. The underside of the wing, between the nacelle and the fuselage was fire damaged. The left engine firewall had scorching and spattering of metal and fire damage at the lower inboard edge of the firewall. The left engine turbocharger inlet air scat tubing was destroyed by fire, along with the oil return line between the bottom of the turbocharger and the aft side of the engine case. This portion of the engine cowling had the most extensive oil deposits and streaking, indicating the breached portion of the oil return line allowed engine oil to vent to the atmosphere. The engine still contained about 6 quarts of oil. The upper oil supply line to the turbocharger was sooted, but not breached. The turbine was free without restriction upon hand rotation. Fire damage and sooting were concentrated on the aft accessory case portion of the engine, centered near the engine driven fuel pump. Examination of the fuel pump disclosed that the fuel line, from the left wing fuel tank to the fuel pump, was not connected to the pump. The threaded fitting of the line was hanging below the pump, and had sooting on the interior of the fitting. The mating inlet nipple of the fuel pump had extensive sooting of the exposed treads. The interior portion of the "L" shaped nipple was sooted. The fuel line from the fuel pump to the engine servo was attached to the pump. It was sooted and scorched, but not breached. Both engines of the twin-engine airplane were removed for overhaul and reinstalled by contracted maintenance personnel. The engines were then ground-run to assess their performance, and to check for any leaks. No leaks were found. An annual inspection was subseqently completed by the operator's maintenance personnel, and the airplane was released for a maintenance test flight. The preflight, engine runup, and the takeoff engine power settings were normal. Another pilot observed the takeoff of the accident airplane, and noticed what appeared to be a slight vapor trail coming from the left engine. He did not report his observations to the pilot. The accident flight was intended to check the turbocharging system by climbing to 12,000 feet. At 8,000 feet, the electrical system experienced a spike, but then returned to normal. As the airplane approached 11,000 feet, the left engine's fuel pressure began to fluctuate. The manifold pressure and rpm began to decrease. The pilot feathered the propeller, and shut-off the engine's fuel/hydraulic valve. The passenger then noticed flames coming from the left engine. The pilot began an emergency descent, and landed on a gravel bar. During the landing roll, the airplane received extensive damage to the fuselage and landing gear. The pilot and passenger exited the airplane and extinguished the flames from the left engine with a hand-held fire extinquisher. A trail of oil was visible on the ground along the airplane's approach path to the accident scene. A postaccident examination of the airplane revealed extensive fire damage, sooting, and oil streaking coming from the left engine nacelle. Inspection of the left engine revealed that the fuel line, from the left wing tank to the engine driven fuel pump, was not connected. The interior threads of the fuel line fitting, and the exterior threads of the fuel pump nipple had extensive sooting. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_ANC03LA032.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗