FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Trans States Airlines Flight 3395

5 Feb 2014 · Memphis, TN, United States

Embraer EMB145 - EP · Accident: hard landing

From George Bush Intercontinental Airport (IAH) to Frederick W. Smith International Airport (MEM)

Report a problem

Event

NTSB case
DCA14FA058
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
Instrument Meteorological Cond

Embraer EMB145 - EP

Aircraft type
Embraer EMB145
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
N802HK
Onboard fatalities
Unknown
Route
From George Bush Intercontinental Airport (IAH), Houston, TXTo Frederick W. Smith International Airport (MEM), Memphis, TN
Aircraft age
About 16 years (built 1998)
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 · 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 systems
  • Organizational issues › Management
  • Personnel issues › Psychological

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

NTSB narrative

After receiving intermittent localizer indications on the airplane’s first approach to the airport, the flight crew, conducted a go-around, and air traffic control cleared the flight for a second approach. The captain indicated that, while the airplane was level at about 2,000 ft on the base leg, the flight entered clouds. The first officer stated that she noted moisture on the windshield wiper and the captain indicated that the wind screen was wet. The cockpit voice recorder (CVR) recorded the captain and first officer briefly discussing ice; however, the airplane’s ice protection system, which was set to the automatic mode, did not operate automatically, and the crew did not activate the system manually. The crew did not see the ice light come on and there were no icing messages on the engine indicating and crew alerting system. As the first officer was applying control inputs to adjust for a crosswind, a rapid roll to the right occurred, which resulted in a wing strike and substantial damage to the airplane. About forty minutes after arrival at the gate, an examination of the airplane found an accretion of ice on the leading edge of both wings. The aircraft performance study, which correlated icing charts with the airplane’s flight profile, determined that the airplane spent over 20 minutes at altitudes where icing was probable during both approaches. The study concluded that the right roll was not commanded by the flight crew but likely due to ice buildup. Although the vertical load factor did not indicate that the airplane experienced a full aerodynamic stall, the ice buildup likely created enough flow separation on one wing for it to lose lift during the flare, without affecting the control of the aircraft in a measurable way during the approach. After the accident, the ice detection and anti-ice systems were tested at the aircraft level with no anomalies identified. The ice detectors were also functionally tested by the manufacturer at the component level with no anomalies identified that could have contributed to the event. A review of FDR data revealed that no failures were recorded for the ice detection system during the accident flight. Additionally, the system operated as expected during a manual preflight test and detected icing conditions during the previous flight. A review of the maintenance records did not reveal any systematic problems with the ice detection system. Therefore, it could not be determined why the ice detection system did not detect the presence of icing conditions even though the airplane accreted ice during the approach. This possibly could have been due to variations in static air temperature that prevented the ice that accumulated on the sensors from reaching the alert threshold or the occurrence of meteorological conditions out of the 14 Code of Federal Regulations Part 25 Appendix C during approach, or a combination of these two factors.” Although the ice detection system did not automatically activate the ice protection system, the CVR recorded a brief discussion during the final approach indicating that the crew was aware that the airplane was picking up “a little bit” of ice. According to the Trans States Airlines EMB145 Airplane Operations Manual (AOM) and Standard Operating Procedures (SOP), even though the airplane is equipped with an ice detector, the crew was responsible for monitoring icing conditions and for manual activation of the ice protection system when necessary. Therefore, the crew recognized that the airplane was operating in icing conditions and accumulating ice and should have manually activated the ice protection system. It is likely the crew's overreliance on automation for the activation and proper operation of the ice and rain protection system resulted in their failure to adequately monitor the system and respond appropriately when it did not activate automatically. Although the AOM and SOPs indicated that the crew is responsible for monitoring icing conditions and for manual activation of the ice protection system when necessary, there was no information in Trans States Airlines ground training modules that presented the crew as being responsible for monitoring and activating the ice and rain protection system when no warnings or cautions were received from the EICAS. Additionally, manual ice detection methods for flight crews to use when flying in potential icing conditions were not specifically referenced during ground training. The Trans States Airlines manager of flight standards said that manual selection of the anti-ice system was not emphasized in training like the automatic mode of operation was during flight operations. It is possible that because the manual operation of the airplane's ice protection system was not emphasized during training, the crew may not have recognized the need to perform this task. Trans States Airlines issued an operations bulletin after the accident that stated interim procedures for crewmembers to follow when operating in potential in-flight icing conditions. The bulletin called for active monitoring of the deicing/anti-icing equipment and, if it did not activate, to accomplish the QRH's Ice Detectors Fail procedures.

Probable cause

the failure of the flight crew to adequately monitor the system for proper operation and manually activate the system during the flight in icing conditions. Contributing to the accident was the crew's limited training on the manual operation of the anti-ice system and the nonactivation of the automatic ice detection system for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA14FA058
Event ID
20140211X00047
Case number
DCA14FA058
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, cause areas. 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: f0ac32ac359154c6abf3831b0a5d47df954c61f30b04979370099b32aec0a07a; retrieved 2026-09-15T23:18:45.935Z.