Mesa Airlines Flight 5733
Embraer 145LR · Accident: loss of control in flight during landing
From Pittsburgh International Airport (PIT) to Roanoke–Blacksburg Regional Airport (ROA)
Event
- NTSB case
- NYC02LA013
- 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
- Visual Meteorological Cond
Embraer 145LR
- Aircraft type
- Embraer 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
- N825MJ
- Operator
- Mesa Airlines
- Onboard fatalities
- Unknown
- Route
- From Pittsburgh International Airport (PIT), Pittsburgh, PATo Roanoke–Blacksburg Regional Airport (ROA), Roanoke
- 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
- 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 in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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
- Pilot in command › Airspeed, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain briefed a "no go-around" for a night visual approach to a "Special Airport." The approach was not stabilized, and the airspeed decreased to the point of a stall. The airplane struck the runway in a nose high pitch attitude, on the aft fuselage, and settled on the landing gear. The first officer made initial callouts of slow airspeed and then stopped when the captain failed to respond to her callouts. After landing, the airplane was taxied to the gate where a post flight inspection limited to the main landing gear did not find the damage. When interviewed, the captain reported that she briefed "no go-around" because no takeoffs were authorized on the runway at night or in IMC conditions; however, the first officer knew this was incorrect, but did not challenge the captain. Both pilots had received CRM training, which included crewmember assertiveness, methods of fostering crew input, and situational awareness, and training on special use airports; however it was not followed by either pilot. The captain's handling of the airplane was outside the parameters specified in the company manuals. Both pilots were described to having good flying skills. The captain said the first officer was passive and quiet. The first officer reported the captain was defensive and did not take criticism very well. A definition of stabilized approach criteria was not found in the company manuals. An FAA Advisory Circular dated August 10, 2000 defined stabilized approach criteria, and actions to be taken if the approach was not stabilized.
Probable cause
the captain's failure to maintain airspeed which resulted in an inadvertent stall/mush, and hard landing. Factors were the failure of both pilots to follow company CRM and flight manual procedures, and the captains improper approach briefing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA013
- Event ID
- 20011030X02159
- Case number
- NYC02LA013
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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 2001-10-17.
- API snapshot SHA-256: 31b2414370598ffd7b6f607a2f797ec536988b9dc9d3026d4bc74b1809ec7993; retrieved 2026-09-18T16:08:58.157Z.