CEN25LA149 · Pphu Ekolot KR-030 TOPAZ
Pphu Ekolot KR-030 TOPAZ · Accident while maneuvering
From Platteville Municipal Airport (PVB) to Platteville Municipal Airport (PVB)
Event
- NTSB case
- CEN25LA149
- 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
Pphu Ekolot KR-030 TOPAZ
- Aircraft type
- Pphu Ekolot KR-030
- 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
- N568RD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Platteville Municipal Airport (PVB), Platteville, WITo Platteville Municipal Airport (PVB), Platteville, WI
- Aircraft age
- About 2 years (built 2023)
- 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
- Maneuvering
- 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
- Unknown or undetermined
- 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
- Not determined › Not determined
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Airplane position data revealed that, after takeoff, the pilot maneuvered within a 4-mile radius of the airport at varying altitudes up to about 2,000 ft mean sea level (msl). Shortly before the accident, the pilot executed a low pass or a touch-and-go and then entered a left turn, climbing the airplane to an altitude of about 1,100 ft msl while turning to a southerly course. The final data point was recorded about 30 seconds later and was located 0.15 miles west of the airport, coincident with the accident site. The ground impact marks relative to the accident site were consistent with a southeasterly course at the time of impact. The position data indicated that the airplane course and groundspeed were about 137° and 78 kts at the end of the data. The recorded surface wind at the airport was from the west (250°) at 7 kts. Accordingly, the corresponding airplane airspeed was about 75 kts. The data did not point to an aerodynamic stall immediately preceding the impact. A postrecovery examination of the airframe and engine did not reveal any anomalies consistent with an inflight failure or malfunction. Data recovered from the onboard engine control unit was consistent with a normally running engine responding to the pilot’s throttle control inputs. From takeoff until the end of the recorded data, each of the engine parameters remained within the specified limitations. The pilot did not recall any aspects of the accident sequence. Based on the available information, the pilot did not maintain clearance to the terrain while maneuvering near the airport. The reason for not maintaining clearance from terrain could not be determined.
Probable cause
The pilot’s failure to maintain clearance from terrain for reasons which could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA149
- Event ID
- 20250409199982
- Case number
- CEN25LA149
- 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: 6a74be388ff762060709a7f5b011b6a5ac8ee1a1b94c56a654b56d25f8be63d8; retrieved 2026-09-16T19:48:21.408Z.