NTSB CAROL · Event
Event ANC22LA035
Registry · N703TH
FAA Aircraft Registry record.
Make / Model
DEHAVILLAND DHC-3
Year of manufacture
1966 · 56 years old at event
Engine
WALTER M601E-11 (751 hp)
Seats / Engines
11 seats · 1 engine
Last airworthiness date
20090918
ADS-B equipped
Yes — Mode-S A96164
Registrant of record
MUNICH HANS W DBA
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to determine the actual weight and balance of the airplane before departure, which resulted in the airplane being operated outside of the aft center of gravity limits and the subsequent aerodynamic stall on final approach. Contributing to the accident was the Federal Aviation Administration's failure to require weight and balance documentation for 14 Code of Federal Regulations Part 135 single-engine operations.
Factual narrative
HISTORY OF FLIGHTOn May 24, 2022, about 1510 Alaska daylight time, a de Havilland DHC-3 Turbine Otter airplane, N703TH, sustained substantial damage when it was involved in an accident near Yakutat, Alaska. The pilot and three passengers were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 on demand charter flight. The flight, operated by Yakutat Coastal Airlines, had departed from Yakutat Airport (PAYA), Yakutat, Alaska, destined for Dry Bay Airport (3AK), Yakutat, Alaska. The pilot reported that during takeoff from PAYA, the tail came up slightly and then fell back to the runway when he attempted to raise the tail of the airplane by applying forward elevator. He thought this was unusual and attributed it to an aft-loaded airplane. The pilot applied additional nose-down trim and departed without incident. He stated that, while en route, the tail of the airplane seemed to move up and down, which he attributed to turbulence. Upon arrival at 3AK, he entered a left downwind for runway 23. At an altitude of about 600 ft, he reduced the power and extended the flaps to 10° abeam the end of the runway. He turned onto the base leg about ½ mile from the approach end of the runway and slowed the airplane to 80 mph. Turning final, he noticed the airplane seemed to pitch up, so he applied full nose-down pitch trim and extended the flaps an additional 10°. On short final, he applied full flaps, and the airplane abruptly pitched up to about a 45° angle. He stated that he applied full nose-down elevator, verified the pitch trim, and reduced the power to idle. When the airplane was about 300 ft above ground level, the airplane stalled, the left wing dropped slightly, and the airplane entered about a 45° nosedown dive. After allowing the airplane to gain airspeed, he applied full back elevator. The airplane impacted forested terrain near the approach end of runway 23 at an elevation of about 18 ft, which resulted in substantial damage to the fuselage, wings, and tail. A Garmin aera 796 was recovered from the accident site. GPS data logs for the day of the accident revealed that the airplane departed at about 1446 and after the initial climb continued southeast for about 18 minutes at GPS altitudes between 492 and 1,280 ft, with a groundspeed between 111 and 127 knots. About 2 minutes before the accident, the airplane initiated a gradual left turn to the east and entered the traffic pattern for the 3AK. For the remainder of the flight the groundspeed varied from 10 knots to 255 knots. The last fully recorded in-flight data point was at 1509, when the airplane was at a GPS altitude of 335 ft with a groundspeed of 13 kts and on a track of 56° (see figure 1). Figure 1 - Accident airplane's flight track. WRECKAGE AND IMPACT INFORMATIONThe cargo was removed from the airplane following the accident without the knowledge or consent of the National Transportation Safety Board (NTSB). A postaccident examination of the airframe and engine, which included an Electronics International MVP-50T engine monitor revealed no pre-accident mechanical malfunctions or failures with the airplane, that would have precluded normal operation. Elevator control continuity was established from the control column in the control cables to the quadrant in the rear of the fuselage at fuselage station (FS) 427 to the elevator control rod to the elevators. Rudder control continuity was established from the rudder pedals to the quadrant at FS 427 to the control rod and to the rudder. . ADDITIONAL INFORMATIONWEIGHT AND BALANCE INFORMATION As a single-engine operation, the flight was not required to have a load manifest on the airplane. The pilot stated that he had computed a weight and balance for the accident flight and recorded it on a piece of paper; however, it could not be located following the accident. At the request of the NTSB, the pilot provided documents indicating the weight of the cargo and passengers and their locations in the airplane. The first set of documents was provided on May 28, 2022, and the values and locations were not consistent with witness statements. A second set of documents was provided on June 10, 2022, that is believed to have more accurately reflected the loading of the accident flight. One passenger reported that the freight had been weighed on pallets and he assisted the pilot by handing him freight that was then loaded on the airplane. He stated there was a pallet of garbage cans that was placed near the front of the airplane, in addition to a pallet of ATV tires, wheels, and a portable sawmill head. Another passenger stated that the airplane was partially loaded when he arrived at the operator’s facility. He was not asked his weight, his bags were not weighed, and he did not see a scale. He stated that he was seated in the back of the airplane with a saw at his feet. According to the weight and balance information for the airplane dated March 15, 2017, the basic empty weight of the airplane was 4,425 lbs with a center of gravity of 141.1 inches. At the airplane’s maximum takeoff gross weight of 8,000 lbs, the center of gravity range was 135.8 inches to 152.2 inches. The airplane’s weight and balance at the time of the accident was estimated using the documentation provided by the pilot on June 10, 2022. The pilot stated that the airplane departed with about 618.8 lbs of fuel and 1,996 lbs of cargo. Assuming an average fuel burn of about 360 lbs/hr, and about 23 minutes of flight time before the accident, fuel onboard at the time of the accident was about 480.8 lbs. The gross weight of the airplane at the time of the accident, was about 7,796.8 lbs. A CG range of about 155.4 - 157.8 inches aft of datum was computed based on the two possible fuel loading extremes. The accident flight was operated under the provisions of Part 135 as an on-demand charter and was subject to the regulation’s applicable rules and the requirements set forth in the company's operations specifications (OpSpecs). Per §135.399, the operator was not allowed to operate the accident airplane without complying with "the takeoff weight limitations in the Approved Flight Manual or equivalent." The requirements of § 135.87 state, in part, that no person may carry cargo (including carry-on baggage) in an aircraft unless it is not located in a position that obstructs the access to, or the use of the aisle between the crew and the passenger compartment (see figure 2). Figure 2 - Accident airplane being loaded for the accident flight. (Source: A passenger on the accident flight) Neither Part 135 for single-engine operations nor the operator's OpSpecs require that the aircraft weight and balance be physically documented for any flight. However, according to OpSpec Paragraph A096, when determining aircraft weight and balance, the operator was authorized to use either the actual measured weights for all passengers, baggage, and cargo or the solicited weights for passengers plus 10 lbs and actual measured weights for baggage and cargo. In addition, for routine operations, the operator was required to follow the weight and balance control procedures outlined in the aircraft weight and balance section of the pilot operating handbook. Although neither Part 135 nor Yakutat Coastal Airlines’ OpSpec requires the operator to physically document the weight and balance for any flights conducted in the company's single-engine airplanes, §135.63 requires that operators using multiengine aircraft are "responsible for the preparation and accuracy of a load manifest in duplicate containing information concerning the loading of the aircraft." This load manifest must be prepared before each flight and include, among other items, the number of passengers, total weight of the loaded aircraft, the maximum allowable takeoff weight, and the center of gravity location of the loaded aircraft. Further, one copy of the load manifest is to be carried in the airplane, and the operator is required to keep the records for at least 30 days. The NTSB attempted to address this single-engine exclusion with the issuance of Safety Recommendations A-89-135, A-99-61, and A-15-29, which asked the Federal Aviation Administration (FAA) to amend the record-keeping requirements of 14 CFR 135.63(c) to apply to single-engine as well as multiengine aircraft. The FAA did not take the recommended action in the above recommendations, and the NTSB classified them "Closed—Unacceptable Action" in 1990, 2014, and 2021, respectively. The purpose of the flight was to transport three passengers and cargo. The pilot reported that, during takeoff, the airplane’s tail came up slightly lowered to the runway when he attempted to raise the tail by applying forward elevator. He stated that he thought this was unusual and attributed it to an aft-loaded airplane. He applied additional nose-down trim and departed without incident. While en route, the tail of the airplane seemed to move up and down, which the pilot attributed to turbulence. Upon arrival at his destination, the pilot entered a left downwind, reduced the power and extended the flaps to 10° abeam the end of the runway. He turned onto the base leg about ½ mile from the approach end of the runway and slowed the airplane to 80 mph. Turning final, he noticed the airplane seemed to pitch up, so he applied full nose-down pitch trim and extended the flaps an additional 10°. On short final he applied full flaps, and the airplane abruptly pitched up to about a 45° angle. He stated that he applied full nose-down elevator, verified the pitch trim, and reduced the power to idle. When the airplane was about 300 ft above ground level, the airplane stalled, the left wing dropped slightly, and the airplane entered about a 45° nose-down dive. After allowing the airplane to gain airspeed, the pilot applied full back elevator. The airplane impacted forested terrain near the approach end of runway 23 at an elevation of about 18 ft. A postaccident examination of the airframe and engine revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation. Elevator and rudder control continuity was confirmed from the cockpit to the respective control surfaces. The airplane's estimated gross weight at the time of the accident was about 7,796 lbs and the airplane's estimated center of gravity was about 3.2 to 5.6 inches beyond the approved aft limit. Maximum gross weight for the airplane is 8,000 lbs. The operator did not comply with their operations specifications and the federal regulations that required them to follow the weight and balance control procedures outlined in the aircraft weight and balance section of the pilot operating handbook and the requirement to maintain an aisle between the crew and passenger compartments. The low speed, left roll, and pitch down of the airplane is consistent with an aerodynamic stall. The additional nose down trim at takeoff, the instability of the airplane during cruise flight, the full nose down trim during the approach and rapid pitch up after the application of full flaps are all consistent with an aft center of gravity (CG) condition of sufficient magnitude that the elevator pitch down authority was insufficient to overcome the pitching moment generated by the loading and aircraft configuration. The full down (or landing) flaps exacerbated the nose-up pitching moment due to the increased downwash on the tail and aft shift of the center of pressure. For each flight in multiengine operations, Title 14 Code of Federal Regulations (CFR) 135.63(c) requires the preparation of a load manifest that includes, among other items the number of passengers, total weight of the loaded aircraft, the maximum allowable takeoff weight, and the center of gravity location of the loaded aircraft; one copy of the load manifest should be carried in the airplane, and the operator is required to keep the records for at least 30 days. Single-engine operations, such as the accident flight, are excluded from this requirement. Had the pilot been required to prepare a load manifest that included the number of passengers, total weight of the loaded aircraft, the maximum allowable takeoff weight, and the center of gravity location of the loaded aircraft, he may have been more aware of the airplane’s out-of-center-of-gravity condition. The National Transportation Safety Board (NTSB) previously addressed the exclusion of single-engine operations from the Part 135 weight and balance requirements with the issuance of Safety Recommendations A-89-135, A-99-61, and A-15-29, which asked the Federal Aviation Administration (FAA) to amend the record-keeping requirements of 14 CFR 135.63(c) to apply to single-engine as well as multiengine aircraft. The FAA did not take the recommended action, and the NTSB classified Safety Recommendations A-89-135, A-99-61, and A-15-29 "Closed—Unacceptable Action" in 1990, 2014, and 2021, respectively. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Pitch control-Attain/maintain not possible
- — Aircraft-Aircraft oper/perf/capability-(general)-(general)-Incorrect use/operation
- — Personnel issues-Task performance-Planning/preparation-Weight/balance calculations-Not specified
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Pitch control-Capability exceeded
- — Aircraft-Aircraft oper/perf/capability-Aircraft capability-CG/weight distribution-Incorrect use/operation
- — Organizational issues-Support/oversight/monitoring-Oversight-Oversight of reg compliance-FAA/Regulator
Verbatim from NTSB's published report. Source file
NTSB_2022_ANC22LA035.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, turbulence). 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 2021 · Journal article (IJAAA)
Comparative Study on the Prediction of Aerodynamic Characteristics of Mini - Unmanned Aerial Vehicle with Turbulence Models
When dealing with CFD simulations the turbulent nature is seen on most of the engineering flows and these flows need to be solved.
- arXiv 2020 · arXiv preprint
Numerical Simulation of Iced Wing Using Separating Shear Layer Fixed Turbulence Models
Aerodynamic prediction of glaze ice accretion on airfoils and wing is studied using the Reynolds-averaged Navier-Stokes method.
- NASA NTRS 2019 · Conference Paper
Prediction of stall and post-stall behavior of airfoils at low and high Reynolds numbers
An interactive boundary-layer method, together with the e(super n)-approach to the calculation of transition, has been used to predict the stall and post-stall behavior of airfoils at low and high Rey…
- arXiv 2026 · arXiv preprint
Direct Numerical Simulations of Ice-Ocean Boundary Turbulence
Turbulent heat and freshwater transport at ice-ocean interfaces controls glacier and iceberg melt rates, yet the underlying physics remains poorly constrained.
- 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 …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
Political Turbulence and Aviation Safety: A Cross-National Analysis of Political Stability's Effects on Aviation Accidents
To what extent does political stability affect aviation safety? This research aims to link domestic political conditions and public safety through the consideration of aviation accident frequency.
Browse the full corpus — academia portal ↗