FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2013 Rediske Air DHC-3 crash

7 Jul 2013 · Soldotna Airport, Soldotna, Alaska, U.S.

Rediske Family Limited Partnership de Havilland DHC-3 · Stall and crash caused by improper loading

From Soldotna Airport (PASX) to Chinitna Bay, AK

Report a problem

Event

NTSB case
DCA13MA121
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
10 · all aircraft and ground
Ground fatalities
Unknown
Occupants
10
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

de Havilland DHC-3

Aircraft type
de Havilland DHC-3
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N93PC
Onboard fatalities
Unknown
Route
From Soldotna Airport (PASX), Soldotna, AKTo Chinitna Bay, AK
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Aerodynamic stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft oper/perf/capability
  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

From the Wikipedia article

On 7 July 2013, a single-engine de Havilland Canada DHC-3 Otter, operated by air charter company Rediske Air, crashed on take-off at Soldotna Airport, Alaska. The sole crewmember and all nine passengers on board were killed. The crash was attributed to improper loading.

Crash

At the time of the accident, the aircraft was being operated by Rediske Air of Nikiski, Alaska, on a commercial charter flight to Bear Mountain Lodge, about 90 mi southwest of Soldotna. According to the United States' Federal Aviation Administration (FAA) and local law enforcement officials, the aircraft "struck the runway and burned" shortly after takeoff from Soldotna Airport, before 11:20 a.m. AKDT (19:20 UTC), killing all 10 people on board. The National Transportation Safety Board (NTSB) was called in to investigate the cause of the crash.

In addition to the pilot, the crash killed nine people from two families visiting Alaska from Greenville, South Carolina. The victims' ages ranged from 11 to 74. The aircraft impacted the ground 2,320 ft from the threshold of the departure runway, about 154 ft to the right of the extended runway centerline, in a nose-low, right-wing-low attitude. An intense post-crash fire consumed most of the aircraft's cockpit and cabin, destroying an unknown quantity of cargo and baggage.

The weather was reported to be cloudy at the time of the accident.

Investigation and cause

Investigation

There were no eyewitnesses to the accident. The incident aircraft was not equipped with a flight data recorder.

The NTSB found that a passenger had recorded the takeoff with the camera of his mobile phone. Due to the absence of any other recorded data, the NTSB decided to reconstruct the trajectory and speed of the airplane based on the recorded video. The analysis was challenging, since the camera was hand-held. By applying image analysis and 3D computer simulation, the NTSB was able to first estimate the time-varying orientation of the camera and then the location and orientation of the airplane. The NTSB report found: "The analysis revealed that shortly after takeoff, flight speed started decreasing rapidly and angle of attack started increasing rapidly. Approximately 11 seconds after takeoff, flight speed and angle of attack reached levels corresponding to stall." The video showed that the aircraft had taken off with its flaps in the full-down or landing position, contrary to the recommendation in the aircraft's flight manual.

The aircraft's engine and flight controls were recovered from the scene of the crash; they did not show signs of mechanical problems nor any damage attributable to causes other than the crash itself. The nature of the propeller and engine damage was consistent with an engine that was rotating and producing power on impact.

Before flying from Nikiski to Soldotna to pick up the passengers, the aircraft had been loaded with what the operator estimated to be 300 lb of food and other supplies for the stay at the fishing lodge, along with 80 lb of baggage. However, no attempt was made to weigh the supplies, nor to calculate the aircraft's center of gravity (CG). Although much of the supplies and baggage was destroyed in the post-crash fire, the NTSB was able to determine the contents based on the manifest, and it found that the supplies actually weighed approximately 720 lb, about 2.4 times what the operator estimated. The operator did not keep detailed fueling records, but a witness saw the pilot fill the forward fuel tank and begin filling the center tank before the flight. Although the cargo was far heavier than estimated and the forward and center fuel tanks were either full or mostly full, the aircraft carried no passengers during its initial positioning flight, and the NTSB concluded that its gross weight and CG had been within acceptable limits at this point; this flight was accordingly uneventful.

The NTSB evaluated several scenarios for the aircraft's estimated takeoff weight from Soldotna, based on the probable amount of fuel left in the tanks after the flight from Nikiski, the weight of the pilot, the reported and autopsied post-crash weights of the passengers, the reported weight of additional baggage loaded at Soldotna, and the weight of baggage recovered after the crash. Although the location of the cargo and baggage within the aircraft could not be precisely determined due to damage, the NTSB concluded that the aircraft was approximately 21 lb overweight on takeoff, with its CG at least 5.5 in aft of the limit in the aircraft's type certificate. Based on the kinematic study conducted using the video evidence, the CG may have been a full 9 in aft of the limit. The NTSB concluded that this condition would have caused the aircraft to pitch up on takeoff and enter an unrecoverable stall even if the pilot immediately applied full nose-down elevator. This was exacerbated by taking off with the flaps fully extended, but the NTSB concluded that the "CG was so far aft of the limit that the airplane likely would have stalled even with the flaps in the correct position."

The NTSB attributed the accident to "The operator's failure to determine the actual cargo weight, leading to the loading and operation of the airplane outside of the weight and center of gravity limits contained in the airplane flight manual, which resulted in an aerodynamic stall." A contributing factor was the operator's failure to require weight and balance documentation for each flight in accordance with FAA regulations.

Text from the Wikipedia article “2013 Rediske Air DHC-3 crash” (revision 1371598879, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

Before picking up the nine passengers, the pilot loaded the accident airplane at the operator's base in Nikiski with cargo (food and supplies for the lodge). The operator of the lodge where the passengers were headed estimated the cargo weighed about 300 pounds (lbs) and that the passengers' baggage weighed about 80 lbs. Estimates of the passengers' weights were provided to the lodge operator in preparation for the trip, which totaled 1,350 lbs. The load manifest listed each of these weight estimates for a total weight of 1,730 lbs and did not contain any balance data. The cargo was not weighed, and the pilot did not document any weight and balance calculations nor was he required to do so.

The airplane operator did not keep fueling records for each flight. A witness who was present during the fueling operations at the operator's base reported that he saw the pilot top off the front tank then begin fueling the center tank. The first leg of the trip from the operator's base to pick up the passengers was completed uneventfully.

According to witnesses at Soldotna Airport, after loading the passengers and their baggage, the pilot taxied for departure. There were no witnesses to the accident. The airplane impacted the ground about 2,320 feet from the threshold of the departure runway and about 154 feet right of the runway centerline. An extensive postcrash fire consumed most of the airplane's cockpit and cabin area, including an unknown quantity of the baggage and cargo. Impact signatures were consistent with a nose- and right-wing-low attitude at impact.

The entire airplane was accounted for at the wreckage site. Disassembly and examination of the engine and propeller revealed that both were operating during impact. Examination of the structure and flight control systems found no preimpact malfunctions or failures that would have precluded normal operation. The pilot was properly certificated and qualified in accordance with applicable federal regulations. Toxicological testing of specimens from the pilot was negative for any carbon monoxide, alcohol, or drugs.

The airplane was not equipped, and was not required to be equipped, with any type of crash-resistant recorder. A video recovered from a passenger's smartphone showed the accident sequence looking out of the row 4 left seat window; the left wing and flaps are in view for most of the sequence and the flap position does not change. The investigation found that the flaps were set to the full-down (or landing) position during takeoff, contrary to recommended procedures in the airplane flight manual (AFM).

The recovered video was used to estimate the airplane speed, altitude, and orientation for the portion of the flight where ground references were visible, about 22.5 seconds after the start of the takeoff roll. For the first 12 seconds, the airplane accelerated linearly from the beginning of the takeoff roll through liftoff. The pitch angle decreased slightly in the first 8 seconds as the tail lifted, remained essentially constant for about 4 seconds, and began to slightly increase as the airplane lifted off. Beginning about 14 seconds after the start of the takeoff roll, the speed began decreasing and the pitch angle began increasing. The pitch angle increased at a constant rate (about 2.8 degrees/second), reaching a maximum value of about 30 degrees, and the ground speed decreased from its maximum of about 68 mph to about 44 mph at the end of the analyzed time. The ground references disappeared from the video frame as the airplane experienced a sharp right roll before impacting the ground several seconds later.

The low speed, rapid right roll, and pitch down of the airplane is consistent with an aerodynamic stall. The constant pitch rate before the stall is 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 aft CG. Additionally, the flaps setting at the full-down (or landing) position, contrary to procedures contained in the AFM, would have exacerbated the nose-up pitching moment due to the increased downwash on the tail and aft shift of the center of pressure; the additional aerodynamic drag from the fully extended flaps would have altered the airplane's acceleration.

Using the data available, the airplane was within weight and balance limitations for the first leg of the trip. However, the cargo loaded was about 2.4 times the weight indicated on the load manifest. Further, the total weight of cargo and baggage in the cargo area, as estimated during the investigation, exceeded the installed cargo net's load limit of 750 lbs by more than 50 lbs. Although the loaded cargo actual weight was higher than indicated on the load manifest, the flight from Nikiski to Soldotna was completed without any concerns noted by the pilot, indicating that even with the higher cargo load, the airplane was within the normal CG range for that leg of the flight. Thus, based on the investigation's best estimate and a calculation of the airplane's weight and balance using the recovered passenger weights, weights and location of the luggage recovered on scene, weight of the cargo recovered on scene, and weights accounting for the liquid cargo destroyed in the postimpact fire, once the passengers were loaded, the airplane weight would have exceeded the maximum gross weight of 8,000 lbs by about 21 lbs and the CG would have been at least 5.5 inches aft of the 152.2-inch limit (a more definitive calculation could not be performed because the exact location of the cargo was not known).

Additionally, the kinematics study of the accident airplane's weight and motion during initial climb and up to the point of stall found that with the pilot applying full pitch-down control input, the CG required to produce the motion observed in the video was likely just past 161 inches. Thus, the only way for the airplane motion to match the motion observed in the video was for the CG to be considerably aft of the 152.2-inch limit, which provides additional support to the results from the weight and balance study. Based on the video study, the weight and balance study constructed from available weight and balance information, and the kinematics study, the airplane exceeded the aft CG limit at takeoff, which resulted in an uncontrollable nose-up pitch leading to an aerodynamic stall. The CG was so far aft of the limit that the airplane likely would have stalled even with the flaps in the correct position.

Neither 14 CFR Part 135 nor the operator's operations specifications (OpSpec) require that the aircraft weight and balance be physically documented for any flights. However, according to Section A096 of the OpSpec, when determining aircraft weight and balance, the operator should 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. The operator did not comply with federal regulations that require adherence to the weighing requirements or the takeoff weight limitations in the AFM. Additionally, although the inaccurate estimate of 300 lbs for the cargo resulted in a calculated CG that was within limits for both legs of the flight, the actual weight of the cargo was significantly higher. Once loaded in Soldotna, the combination of the passengers, their baggage, and the actual cargo weight and its location resulted in the CG for the accident flight being significantly aft of the limit. With the CG so far aft, even with full nose-down input from the pilot, the nose continued to pitch up until the airplane stalled.

For each flight in multiengine operations, 14 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 CG 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 are excluded from this requirement. The NTSB attempted to address this exclusion with the issuance of Safety Recommendations A-89-135 and A-99-61, 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 either instance, and the NTSB classified Safety Recommendations A-89-135 and A-99-61 "Closed—Unacceptable Action" in 1990 and 2014, respectively.

Probable cause

The operator's failure to determine the actual cargo weight, leading to the loading and operation of the airplane outside of the weight and center of gravity limits contained in the airplane flight manual, which resulted in an aerodynamic stall. Contributing to the accident was the Federal Aviation Administration's failure to require weight and balance documentation for each flight in 14 Code of Federal Regulations Part 135 single-engine operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

Wikipedia article: 2013 Rediske Air DHC-3 crash
Article
2013 Rediske Air DHC-3 crash
Revision
1371598879 · 2026-08-27 · retrieved 2026-09-18
Wikidata
Q13642546
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA13MA121
Event ID
20130707X14623
Case number
DCA13MA121
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "2013 Rediske Air DHC-3 crash" (page 39898151, revision 1371598879); merged with NTSB case DCA13MA121 (events / aircraft)
Date
NTSB record DCA13MA121: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
Place and country
Wikipedia infobox: site; country from NTSB record DCA13MA121
Map position
NTSB record DCA13MA121: NTSB API eventLatitude/eventLongitude
Aircraft, operator and route
NTSB record DCA13MA121: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record DCA13MA121: operated under Part 135: Air Taxi & Commuter
Fatalities
NTSB record DCA13MA121: NTSB API totalFatal
Ground fatalities
NTSB record DCA13MA121: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "2013 Rediske Air DHC-3 crash" and NTSB case DCA13MA121, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.