ERA23LA376 · Embraer S A EMB-545 MOD
Flexjet Embraer S A EMB-545 MOD · Accident: hard landing
From Westchester County Airport (HPN) to St Simons Island Airport (SSI)
Event
- NTSB case
- ERA23LA376
- 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
- 0
- 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
- General aviation
- 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 S A EMB-545 MOD
- Aircraft type
- Embraer EMB-545
- 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
- N434FX
- Operator
- Flexjet
- Onboard fatalities
- Unknown
- Route
- From Westchester County Airport (HPN), White Plains, NYTo St Simons Island Airport (SSI), St.Simons Island, GA
- Aircraft age
- About 3 years (built 2020)
- 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 91 Subpart K: Fractional
- 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 oper/perf/capability
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the flight crew, the departure and en route phases of the flight in the airplane were uneventful. Gusting wind and visual conditions existed at the destination airport, and the pilot chose to fly a GPS approach (versus a visual pattern) to allow more time for alignment and set-up for landing. The flight crew reported that all checklists and callouts were conducted. During the approach with the autothrottles engaged, the approach was stable as the airplane descended through 500 ft above ground level (agl). After the copilot made the “500 ft stable” callout, the airplane continued its descent, then crossed over a small section of trees. The pilot reported that he felt an “uplift,” then the airplane began to porpoise when it was about 100 to 150 ft agl. The pilot tried to make pitch corrections, but the airplane’s attitude did not change as commanded. The copilot tried to assist but observed the same airplane response. The airplane landed hard and slid along the runway, coming to rest in the grass off the right side of the runway. Although the flight crew at times engaged in nonessential conversation while approaching the airport, there is no indication that this contributed to the accident. Further, review of data from the engines’ full authority digital engine controls did not reveal any anomaly that would have contributed to the accident. The airplane was equipped with a fly-by-wire flight control system that featured an angle of attack (AOA) limiter protection system (instead of a traditional stall warning system) designed to prevent the airplane from stalling by limiting its AOA. Review of flight data recorder (FDR) data indicated that the AOA limiter protection engaged during the approach due to a sudden increase in AOA when the airplane was at a radio altitude of 162 ft. The sudden AOA increase was likely due to a wind gust. The airplane’s AOA then quickly reduced from 12.8° to less than 5° and remained below the engagement threshold for the remainder of the flight, but the AOA limiter protection remained engaged. Although the AOA limiter protection performed as designed, it reduced the flight crew’s ability to pitch up the airplane during the flare. For example, the pilot used the sidestick to command full airplane-nose-up pitch for about 3 seconds before touchdown, but the fly-by-wire system provided less than 3°of airplane-nose-up elevator. About 1.5 seconds before touchdown, the copilot also used the sidestick to command full airplane-nose-up pitch, but the fly-by-wire system responded with 5.5° of airplane-nose-down elevator. Neither flight crewmember indicated any awareness that the AOA limiter protection had engaged. During the flare, the airplane was subjected to a horizontal gust which resulted in a reduction of about 8 kts of indicated airspeed and the airplane touched down hard. An NTSB performance study determined that, at the time the airplane touched down hard, about 10° of AOA or stall margin remained that the flight crew was unable to use during the landing because the AOA limiter protection was engaged. The flight control computer software version current at the time of the accident would allow AOA limiter protection disengagement only on having three conditions met: 1) AOA reduced to values below the engagement threshold, 2) airspeed above a factor of stall speed threshold, and 3) difference between the normal load factor demand determined by the sidestick pitch command and the airplane’s actual load factor being below a specified threshold. Review of FDR data revealed that the frequency and amplitude of the pilot’s oscillating sidestick pitch commands prevented AOA limiter protection disengagement due to condition 3. About 7 months after the accident, the FAA issued airworthiness directive (AD) 2024-05-13, which required revisions to the airplane flight manual (AFM) to incorporate new operational airspeed limitations, flight control limitations, and approach procedures when the AOA limiter protection is engaged. This interim safety measure mandated the actions specified in the National Civil Aviation Agency of Brazil (ANAC) AD 2024-02-02, which was issued about 2 months earlier. Subsequently, about 22 months after the accident, ANAC issued AD 2024-02-02R1, which superseded ANAC AD 2020-02-02 and required a software update to the flight control computers to revise the AOA limiter protection criteria, which included allowing for a higher pitch response to sidestick movement while the AOA limiter protection is engaged and allowing for it to disengage any time there is a sidestick pitch-down command and conditions 1 and 2 are satisfied. The FAA indicated that it planned to release its final rule regarding the Embraer EMB-545 and EMB-550 AOA limiter about September 2026.
Probable cause
The control laws of the angle of attack limiter protection system, which precluded the system from disengaging during an approach in gusting wind conditions, limiting the flight crew’s ability to control the airplane’s pitch and resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA376
- Event ID
- 20230921193114
- Case number
- ERA23LA376
- 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: 0fecabfbc861a46e2ddd673937e49b66225bf2bb8d5b7fccfa42b199be6b7e6d; retrieved 2026-09-16T18:08:49.758Z.