Compass Airlines Flight 5763
Embraer ERJ170 200LR · Accident: turbulence encounter en route
From John Wayne Orange County International Airport (SNA) to Reno Tahoe International Airport (RNO)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DCA19CA081
- 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 ERJ170 200LR
- Aircraft type
- Embraer ERJ170
- 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
- N613CZ
- Operator
- Compass Airlines
- Onboard fatalities
- Unknown
- Route Possible conflict
- From John Wayne Orange County International Airport (SNA), Santa Ana, CATo Reno Tahoe International Airport (RNO), Reno, NV
- Aircraft age
- About 11 years (built 2008)
- 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
- En route · cruise
- 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
- Turbulence encounter
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On February 13, 2019 about 1232 PST, Compass Airlines flight 5763, an Embraer ERJ 175, N613CZ, encountered turbulence while in cruise flight at flight level (FL) 340 and subsequently diverted to Reno-Tahoe International Airport (KRNO), Reno, Nevada. Of the 75 passengers and crew onboard, one flight attendant sustained serious injuries while two flight attendants and two passengers received minor injuries. The airplane sustained minor damage. The flight was operating under the provisions of 14 Code of Federal Regulations Part 121 as a regularly scheduled passenger flight from the John Wayne-Orange County Airport (KSNA), Santa Ana, California to Seattle-Tacoma International Airport (KSEA), Seattle, Washington. According to the flight crew, about 40 minutes into the flight when the airplane was in smooth air and “between cloud layers”, the captain informed the flight attendants that they could begin cabin service but left the seatbelt sign illuminated for passengers because there was a report of ”occasional light chop”. About 20 minutes later, the flight encountered an area of severe turbulence that lasted about 8 seconds and caused the airplane to rapidly gain altitude and the traffic collision avoidance system (TCAS) to issue a resolution advisory (RA) for opposite-direction traffic 1,000 ft above them. The first officer (FO) , who was the flying pilot, disengaged the autopilot and applied forward control pressure to comply with the RA. The FO could not obtain the target flight path vector directed by the TCAS, so the captain assisted on the controls to obtain the desired pitch attitude. After the airplane descended back to its assigned altitude, the TCAS RA cleared, and the captain informed air traffic control of the turbulence and TCAS RA. According to the flight attendants (FA), the turbulence was encountered as they were beginning the beverage service. Two of the FAs impacted the ceiling before falling to the floor and one passenger, who had been in the lavatory at the time of the encounter had a small head laceration. As a result of the injuries, the captain declared an emergency and the flight diverted to KRNO. The FA in the aft galley was assisted by a medically qualified passenger and remained on the floor until landing due to her injuries. She was transported to the hospital and diagnosed with a broken arm. Post accident examination of the weather satellite data depicted cloud patterns aloft consistent with the presence of a convective updraft coincident with the flight’s location at the time of the turbulence encounter. The convection appeared to be “embedded” with stratiform clouds and may not have been visually identifiable by the flight crew.
Probable cause
an inadvertent encounter with convective turbulence that resulted in a TCAS RA, which required an abrupt control input by the flight crew to resolve the conflict.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA19CA081
- Event ID
- 20190214X42337
- Case number
- DCA19CA081
- 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: 0808db4cfacf4ac0047a74fe64b39962634cf2e1d2c133e46e0c00a1e116625b; retrieved 2026-09-16T08:35:47.265Z.