FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Eagle Flight 3400

24 Feb 2007 · Dallas, TX, United States

Embraer EMB-145LR · Incident: loss of control on ground/water during landing

From San Antonio International Airport (SAT) to Dallas Love Field (DAL)

Report a problem

Event

NTSB case
DFW07IA077
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
Incident
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
N648AE
Onboard fatalities
Unknown
Route
From San Antonio International Airport (SAT), San Antonio, TXTo Dallas Love Field (DAL), Dallas, TX
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 · landing roll
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
Loss of control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Pilot in command › Directional control, not maintained

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

NTSB narrative

The 4,274-hour airline transport pilot lost control of the airplane while landing on a 7,752-foot long, by 150-foot wide runway, with a prevailing crosswind. The airplane drifted off the right side of runway 31R. A review of the flight data (FDR) and cockpit voice recorders (CVR), revealed that for the first ten seconds after touchdown the number 3 brake received more brake pressure than the number 1 brake. Also, for the four seconds that thrust reversers were utilized, the number 2 engine was brought to a higher N1 than the number 1 engine. Just prior to touching down, the tower reported winds from 250 degrees at 27 knots, with gusts to 38 knots. The operator used tabular data in determining crosswind component without having to utilize a graph. Utilizing the graph, the crosswind component was approximately 33 knots. According to the Airplane Flight Manual, the maximum demonstrated crosswind for the airplane is 30 knots.

Probable cause

The pilot's failure to maintain directional control of the airplane while landing with a crosswind. A contributing factor was the prevailing crosswind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW07IA077
Event ID
20070228X00237
Case number
DFW07IA077
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: 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: 9e436f65d388edab0996b592fe7db82eaf886fc737baca1d9e7ff72b21118f05; retrieved 2026-09-18T14:46:38.831Z.
  • The NTSB's operator name is blank for N648AE; the operator shown is the name the NTSB records it doing business as.