# Incident 20260518010169I: Aeroprakt Mfg Sp Z O O A32, Waukesha, WI, May 18, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 18, 2026, 15:33 local time
- Place: Waukesha, WI
- Airport: Waukesha County Airport
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 43.0410° N, 88.2371° W: Placed by OpenAirDocs at WAUKESHA COUNTY (UES), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.0410&lon=-88.2371&mi=10
- Aircraft: N284RK, registered now (https://openairdocs.org/aircraft/N284RK) (OpenAirDocs)
- Registry model: Aeroprakt Mfg SP Z O O A32 (registry code 06001B4, https://openairdocs.org/model/aeroprakt-mfg-sp-z-o-o-a32) (OpenAirDocs)
- Registry engine: Rotax 912 IS series (registry code 55593, https://openairdocs.org/engine/rotax-912-is-series) (OpenAirDocs)
- Reported make and model: AEROPRAKT MFG SP Z O O A32
- Reported engine: ROTAX 912 IS
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, private pilot, student
- Pilot flight hours: 437 total, 16 in this make and model, 16 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260518010169I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON 18 MAY, 2026 ^PRIVACY DATA OMITTED^ WHILE TAKING A SINGLE ENGINE COMMERCIAL CHECK RIDE, HAD A HARD LANDING AT KUES, CREATING LIGHT DAMAGE ON THE TAIL OF AIRCRAFT ^PRIVACY DATA OMITTED^.  DURING THE APPROACH TO LANDING HE WAS GIVEN CLEARANCE TO LAND ON RUNWAY 18, NUMBER 2 BEHIND A LANDING AIRCRAFT.  MR. KAWAMUA STATED THAT HE HAD THE AIRCRAFT IN SITE.  THE DPE ON BOARD DID NOT HAVE THE AIRCRAFT IN SITE.  MR. KAWAMURA TURNED ON BASE AND THE TOWER QUESTIONED AGAIN IF HE HAD THE AIRCRAFT IN SITE AND AGAIN HE STATED YES.  THE DPE HAVING ACQUIRED THE AIRCRAFT ASKED TOWER PERMISSION TO DO A SPACING TURN IN ORDER TO GIVE THE OTHER AIRCRAFT SOME ROOM AND THEY FELT THEY WERE TOO CLOSE.  AFTER COMPLETING THE SPACING TURN MR. KAWAMURA TOOK BACK CONTROL OF HE AIRCRAFT AN ON ATTEMPTING TO LAND DID NOT HAVE THE AIRCRAFT IN A COORDINATED MANNER AND IT LANDED HARD ON THE RUNWAY.  THE DPE THEN TOOK CONTROL OF THE AIRCRAFT AGAIN AS IT VEERED OFF THE RUNWAY INTO THE GRASSY AREA BETWEEN THE RUNWAY AND TAXIWAY.

UPON INTERVIEWING MR. KAWAMURA HE STATED THAT HE IN FACT DID NOT HAVE THE OTHER AIRCRAFT IN SITE WHEN HE RESPONDED TO TOWER TWICE.  HE THAN ALSO INDICATED THAT HE EXCEEDED THE CROSS WIND COMPONENT OF THE AIRCRAFT BY 3 DEGREES WHICH WAS THE LEADING FACTOR TO THE UNSTABILIZED APPROACH.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.