CEN24LA282 · Just HIGHLANDER JA20
Just HIGHLANDER JA20 · Accident: hard landing
From Valparaiso, IN to an unrecorded destination
Event
- NTSB case
- CEN24LA282
- 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
Just HIGHLANDER JA20
- Aircraft type
- Just HIGHLANDER
- 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
- N707KM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Valparaiso, INTo not recorded
- Aircraft age
- Built the same year (2024)
- 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
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that when the airplane was on short final to land on a grass airstrip, close to the ground, the wing flaps retracted from 40° to 0° uncommanded, and the airplane started to sink. The pilot added engine power to arrest the descent; however, the airplane landed hard. The pilot taxied the airplane without further incident. A postlanding examination of the airframe revealed substantial damage to the fuselage on the right side. After the accident, the flaps were manipulated in and out of the fully extended flap position using the flap actuator handle. The flap controls were continuous and extended and retracted as designed. The flap actuator handle always remained secure in the detent. Investigators were unable to duplicate the uncommanded retraction of the flaps from 40° to 0°. There were no mechanical anomalies with the airplane or related systems that would have precluded normal operations.
Probable cause
The reported uncommanded retraction of the flaps while on short final for unknown reasons, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA282
- Event ID
- 20240723194753
- Case number
- CEN24LA282
- 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: 75aee675b29ad9ee8f9ea1877b72605e18c7c3ba8aae73a789fd10a64743f134; retrieved 2026-09-16T19:04:42.441Z.