The U.S. aircraft register, updated daily
Accidents · NTSB DCA14FA058 · Final report

Embraer EMB145 - EP accident near Memphis, Tennessee, February 5, 2014

On February 5, 2014 at about 6:22 am local time, a 1998 Embraer EMB145 - EP, registered N802HK, was substantially damaged in an accident during landing (flare/touchdown) near Memphis, Tennessee (Memphis International Airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 53 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 5, 2014 · about 6:22 am local time
Place
Memphis, Tennessee · Memphis International Airport · map
Type
Accident
Injuries
No one was hurt; 53 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Embraer EMB145 - EP EP, built 1998 · all EMB145 - EPs on the register
Registration
N802HK · no longer on the register · serial 145066
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Structural icing during approach (IFR missed approach)
  2. Aerodynamic stall/spin during landing (flare/touchdown)
  3. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Flight crew
  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to structural icing › Awareness of condition
  • Organizational issues › Management › Policy/procedure › Adequacy of policy/proc › Training organization
  • Aircraft › Aircraft systems › Ice/rain protection system › Airfoil anti › ice, deice › Not used/operated
  • Aircraft › Aircraft systems › Ice/rain protection system › Ice detection › Unknown/Not determined

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 6,409 hours in all; 5,641 in this make and model; 176 in the last 90 days; 49 in the last 30 days; 1,797 as pilot in command; 432 on instruments
  • Last flight review: December 15, 2013
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, flight instructor
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 2,075 hours in all; 925 in this make and model; 16 in the last 90 days; 55 in the last 30 days; 1,080 as pilot in command; 822 on instruments
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 34,069 hours
  • Last inspection: continuous airworthiness programme, February 3, 2014
  • Maximum gross weight: 43,935 lb
  • Seats: 54
  • Landing gear: retractable
  • Engine 1: Rolls-Royce AE3007A1 (turbojet); 27,422 hours total
  • Engine 2: Rolls-Royce AE3007A1 (turbojet); 20,181 hours total
  • Operator: Trans States Airlines, LLC

The flight

  • Departed from: IAH Houston TX at 2:22 am
  • Destination: MEM Memphis TN
  • Flight plan: IFR
  • Runway 36R, 9,000 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 290° at 7 knots
  • Visibility: 1 statute miles
  • Sky: overcast; ovct
  • Temperature: 34°F (1°C), dew point 30°F (-1°C)
  • Altimeter: 29.92 inHg
  • Observation at 5:54 pm from MEM, 1 miles away

Injuries

FatalSeriousMinorNone
Cabi1
Flight crew2
Passengers50

Documents from the investigation the NTSB's docket: the evidence folder behind the report

21 documents, released by the NTSB on February 18, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Aircraft Performance PDF, 15 pages View Download
2 Operations Factual Report of Group Chairman PDF, 26 pages View Download
3 Operations Factual Report - Attachment 1 PDF, 48 pages View Download
4 Operations Factual Report - Attachment 2 PDF, 1 page View Download
5 Operations Factual Report - Attachment 3 PDF, 1 page View Download
6 Operations Factual Report - Attachment 4 PDF, 10 pages View Download
7 Operations Factual Report - Attachment 6 PDF, 1 page View Download
8 Operations Factual Report - Attachment 7 PDF, 9 pages View Download
9 Systems Group Chairman's Factual Report PDF, 13 pages View Download
10 Operations Group Letter from Tsa on Use of Confidential and Proprietary Information PDF, 1 page View Download
11 Flight Data Recorder Specialist's Factual Report PDF, 12 pages View Download
12 Flight Data Recorder Specialist's Factual Report - Attachment 1 data file Download
13 Flight Data Recorder Specialist's Factual Report - Attachment 2 data file Download
14 Meteorology Factual Report PDF, 24 pages View Download
15 Meteorology Independent Icing Study PDF, 60 pages View Download
16 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 14 pages View Download
17 Cockpit Voice Recorder - Group Chairmana��s Factual Report PDF, 61 pages View Download
18 Cockpit Voice Recorder - Group Chairmana��s Factual Report - Attachment 1 PDF, 9 pages View Download
19 Evidence Control Form - Switch PDF, 1 page View Download
20 Release of Wreckage Form PDF, 1 page View Download
21 Pilot Statements PDF, 2 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.