ExpressJet Airlines Embraer EMB-145LR incident
Embraer EMB-145LR · Incident: runway excursion during landing
Event
- NTSB case
- OPS11IA271
- 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
- N13964
- Operator
- ExpressJet Airlines
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- 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
- Runway excursion
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to the flight landing on runway 6R, airport maintenance crews reported ice on runway 6L and the possibility of ice on runway 6R. A local air traffic controller relayed the information on possible runway conditions on runway 6R to the flight crew prior to landing; there were no braking action advisories in effect. While landing, the airplane departed the left side of runway 6R several hundred feet from the intersection of runway 6R and runway 36, coming to a stop on runway 36 facing northeast. Airport damage consisted of a damaged runway distance remaining marker. There were no injuries to the passengers or crew and the airplane suffered damage to the left main gear door, auxiliary gear door, and the No. 2 main tire.
A special weather observation taken after the incident reported wind from 070 at 8 knots, visibility of 7 miles in light freezing rain, an overcast ceiling at 1,900 feet above ground level, a temperature of -4 degrees Celsius, a dew point of -8 degrees Celsius, with the altimeter indicating 30.10 inches of mercury. Freezing rain began about 3 minutes prior to the incident and an accumulation of .01 inches of snow had fallen in the 14 minutes prior to the start of the freezing rain.
Probable cause
The pilots' lack of consideration for developing and known weather conditions en route to and at the destination airport, resulting in a runway excursion and subsequent incursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS11IA271
- Event ID
- 20110207X84026
- Case number
- OPS11IA271
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-02-01.
- API snapshot SHA-256: 84ffb2d3c76ce453f78fad56fd35055ecd2b1d9d8acfe45b8f231f2817df5cbe; retrieved 2026-09-15T15:46:38.788Z.