FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Trans States Airlines Embraer EMB-145LR accident

14 Aug 2008 · St. Louis, MO, United States

Embraer EMB-145LR · Accident: tailstrike during landing

From Jacksonville International Airport (JAX) to St. Louis Lambert International Airport (KSTL)

Report a problem

Event

NTSB case
DFW08CA215
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
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
Airline
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

Embraer EMB-145LR

Aircraft type
Embraer EMB-145
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
N814HK
Onboard fatalities
Unknown
Route
From Jacksonville International Airport (JAX), Jacksonville, FLTo St. Louis Lambert International Airport (KSTL), St. Louis, MO
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 121: Air Carrier
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
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
Tailstrike
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

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

NTSB narrative

While en route to the destination airport, the first officer (FO) warned that his flaps 45 degrees landings are "a little extreme." The FO continues by stating that the landings are "a little non-standard, but it’s way more fun." The flight data recorder (FDR) showed an increase in the airplane's pitch angle at approximately 34 feet above ground level. The landing flare continued to increase to approximately 13 degrees of pitch angle with a corresponding angle of attack of 17 degrees. The airplane's stick shaker/stall warning system activated seconds before the landing, during which the airplane's tail section contacted the runway.

Probable cause

The flying pilot's excessive angle of attack during the landing flare resulting in abnormal runway contact.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08CA215
Event ID
20081003X17330
Case number
DFW08CA215
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: 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.
  • API snapshot SHA-256: d9801563537d539b653b9818af6c9bfe6cbf4081f880ae9f3a7f52b08e835e3a; retrieved 2026-09-15T10:16:47.315Z.