FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ameriflight Swearingen SA227 AC accident

4 Sept 2020 · San Antonio, TX, United States

Swearingen SA227 AC · Accident: hard landing

From Del Rio International Airport (DRT) to an unrecorded destination

Report a problem

Event

NTSB case
CEN20LA440
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
Unknown
Ground fatalities
Unknown
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

Swearingen SA227 AC

Aircraft type
Swearingen SA227
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
N362AE
Operator
Ameriflight
Onboard fatalities
Unknown
Route
From Del Rio International Airport (DRT), Del Rio, TXTo not recorded
Aircraft age
About 33 years (built 1987)
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
Landing · flare/touchdown
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
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was concluding the Part 135 cargo flight when the airplane landed hard and departed off the right side of the runway. The pilot reported that the airplane was flying wings level with the nose aligned with the runway and on a normal glidepath to the runway until it crossed over the runway threshold. He stated that the airplane entered a right roll shortly after he reduced engine power for the landing flare, and that the roll became more pronounced as the landing flare continued. He was unable to regain control of the airplane before it landed hard on the right main landing gear with the airplane rolled about 20° right-wing-down. The airplane then departed off the right side of the runway where the nose landing gear collapsed. The fuselage, right engine nacelle, right-wing main spar, and forward pressure bulkhead were substantially damaged during the hard landing.

A review of automatic dependent surveillance-broadcast (ADS-B) data revealed that the pilot did not fly a stabilized approach as defined by the operator’s general operations manual. Specifically, the airplane’s descent rate exceeded the operator’s 1,000 feet per minute (fpm) limitation, the airplane’s airspeed was not maintained at the specified approach speed, and the airplane was not wings level and aligned with the runway at 300 ft above the touchdown zone elevation. At 1,000 ft above the touchdown zone elevation, the airplane was descending on the base leg at 2,055 fpm and was 5 knots below the specified approach speed. During the left turn from base leg to final approach the airplane’s descent rate reached 2,929 fpm, which was nearly 3 times the operator’s limitation for a stabilized approach. The airplane crossed over the runway threshold about 43 ft above ground level while in a 1,015 fpm descent. About 3 seconds later, the airplane touched down on the runway while descending 733 fpm and 36 ft right of the centerline with a ground track about 1.5° right of the runway course. The airplane came to rest in the grass infield between the runway and a taxiway.

Although the pilot postulated that the right roll during the landing flare was due to a right engine malfunction, his recollection of the airplane’s flight path to the runway was not consistent with the recorded ADS-B data. The pilot’s failure to fly a stabilized approach resulted in an excessive descent rate, hard landing, and loss of control. Additionally, postaccident examination revealed no evidence of a preexisting mechanical malfunction or failure that would have precluded normal operation of the airplane.

Probable cause

The pilot’s failure to fly a stabilized approach which resulted in a hard landing and loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20LA440
Event ID
20210210102619
Case number
CEN20LA440
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2020-09-05.
  • API snapshot SHA-256: 11513aff5fffcae22556d906350ccc6afe1f4e79ac513a5de040d1f4a8cbe9a3; retrieved 2026-09-16T13:37:41.119Z.