ERA23LA291 · Volato 400
Volato 400 · Accident: abnormal runway contact during landing
Event
- NTSB case
- ERA23LA291
- 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
Volato 400
- Aircraft type
- Volato 400
- 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
- PR-ZVL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 10 years (built 2013)
- 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: General Aviation
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that upon returning from a local flight, during the landing flare, he noticed the airplane was still sinking so he “began pulling back on the stick.” The airplane continued to sink, and the pilot added partial power, but the sink rate was not arrested, and the airplane impacted the ground, about 10 ft before the runway threshold. Upon impact with the ground, the nose landing gear collapsed, and the airplane slid about 1,000 ft down the runway. Postaccident examination of the airplane by a Federal Aviation Administration (FAA) inspector found substantial damage to the firewall. The pilot reported that he felt he used full elevator aft but did not think he was getting full authority and that an autopilot servo bracket may have interfered with the flight control. The safety pilot on board reported that the pilot performed a flight control check before the departure with no anomalies noted. Additionally, during a postaccident examination of the flight controls, the FAA inspector found the autopilot servo bracket was loose on the elevator control tube and a flight control check found the bracket did not restrict the aft movement of the elevator. The postaccident examination otherwise found no evidence of any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s improper landing flare which resulted in a runway undershoot and a hard landing, which substantially damaged the airplane’s firewall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA291
- Event ID
- 20230707192553
- Case number
- ERA23LA291
- 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, 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: 1fdf31f3aa5936efc077ec4b5f9b133bce2eb42a51c3ea398cfa06666ac962dc; retrieved 2026-09-16T17:49:17.093Z.