Ameriflight Beech 1900C accident
Beech 1900C · Accident: hard landing
From Portland International Airport (PDX) to Seattle–Tacoma International Airport (SEA)
Event
- NTSB case
- SEA97FA188
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Beech 1900C
- Aircraft type
- Beechcraft 1900
- 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
- N3172A
- Operator
- Ameriflight
- Onboard fatalities
- Unknown
- Route
- From Portland International Airport (PDX), Portland, ORTo Seattle–Tacoma International Airport (SEA)
- 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
- Landing · flare/touchdown
- First occurrenceThe 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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
- Dispatcher › Aircraft weight and balance, inaccurate
- Fuel system › Leak
- Landing gear › Overload
- Stall/mush
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Beech 1900C cargo aircraft was loaded with more than 4,962 pounds of cargo during an approximate 20 minute period. No scale was available at the aircraft, forcing loaders to rely on tallying either waybill weights or estimates of total cargo weight and center of gravity (CG) during the brief loading period. Additionally, a strike had shut down a major cargo competitor at the time with substantial cargo overflow to the operator. Post-crash examination determined the cargo load was 656 pounds greater than that documented on the pilot's load manifest, and the CG was between 6.8 and 11.3 inches aft of the aft limit. The airplane behaved normally, according to the pilot, until he initiated full flaps for landing approaching the threshold of runway 34L at the Seattle-Tacoma International airport. At this time, the aircraft's airspeed began to decay rapidly and a high sink rate developed as the aircraft entered into a stall/mush condition. The aircraft then landed hard, overloading the nose and left-main landing gear which collapsed. A post-impact fuel system leak during the ground slide led to a post-crash fire.
Probable cause
A stall/mush condition resulting from an aft center of gravity which was inaccurately provided to the pilot-in-command by contractual cargo-loading personnel. Additional causes were overloading of the aircraft's landing gear and fuel leakage resulting in a post-crash fire. Factors contributing to the accident were the pilot's improper lowering of flaps in an aft CG situation and the inadequate company procedures for cargo loading.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA97FA188
- Event ID
- 20001208X08740
- Case number
- SEA97FA188
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-08-14.
- API snapshot SHA-256: 8da0603b70a97a8fc96a8b66a58fd3b3bbbd72abe8fe98205f023f6404422995; retrieved 2026-09-18T17:27:01.384Z.
- The NTSB's operator name is blank for N3172A; the operator shown is the name the NTSB's other records give its FAA operator code, JIKA.