ERA26LA090 · Devesh Tiwary LIGHTNING XS
Devesh Tiwary LIGHTNING XS · Accident: loss of control on ground during landing
From Daytona Beach International Airport (DAB) to an unrecorded destination
Event
- NTSB case
- ERA26LA090
- 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
- Event fatalities
- Unknown
- 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
- 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
Devesh Tiwary LIGHTNING XS
- Aircraft type
- Devesh Tiwary LIGHTNING XS
- 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
- N929XS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo not recorded
- Aircraft age
- About 1 year (built 2025)
- 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 · landing roll
- 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
- Loss of control on ground
- 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 he was attempting to land the airplane on a 4,425-ft-long asphalt runway. During his first approach, the airplane was too high and he performed a go-around. During the second approach, the airplane floated for about 1,000 ft in ground effect before touchdown. The pilot applied gently braking initially, but then heavier braking as the airplane neared the end of the runway. During the heavy braking, the airplane veered left off the runway and onto grass. It traveled into a ditch before coming to rest upright. The forward portion of the fuselage, including the engine mounts, were substantially damaged during the accident sequence. The pilot added that there were no preimpact mechanical malfunctions with the airplane.
Probable cause
The pilot’s failure to maintain directional control during landing, which resulted in a runway excursion and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA26LA090
- Event ID
- 20260109202279
- Case number
- ERA26LA090
- 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: 3325412c0b35a99a26aa9e00897b515d4bcc6ca48c98a7dbf75152af52b077ed; retrieved 2026-09-16T20:39:49.293Z.