20250821014789I

Incident · Minor damage

FAA incident report · Nighthawk NH-2 · Ravenna, OH · August 21, 2025

Date
August 21, 2025 · 19:40 local
Place
Ravenna, OH
Airport
Portage County
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N86BZ
Reported as
Nighthawk NH-2
Reported engine
SAFRAN SR305-230 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Airline transport
Pilot’s flight hours
10,300 total360 in this make and model20 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Incident reported to FSDO by airport manager. Incident occurred the previous evening. Tried contacting privacy data omitted to no avail. Sent registered mail to privacy data omitted received reply from privacy data omitted stating the aircraft had a prop strike with no other operational damage. Citing 49 CFR part 830.2, he did not believe it merited further investigation. Sent response to lawyer citing 49 CFR § 44709, allows for the administreator to reinspect at any time a civil aircraft. After this notice the aircraft was made available for inspection. Pilot in command reported that after about thirty minutes of pattern work, crew executed a standard pattern touch and go landing. While on crosswing and at pattern altitude PIC initiated a simulated engine failure. Once initiated this called for a return to the airport to land in the opposite direction of the touch and go. PIC reported that while the checklist was out and in use the crew failed to lower the gear. PIC attributed this to being distracted by a discussion on dive brake deployment and propeller settings. First indication of the gear up condition was the belly scraping on the runway. The propeller struck the runway shortly thereafter. PIC reported the aircraft was controlable to a stop. Damage observed to the propeller and the nonstructural belly of the aircraft. Damage is not substantial by definition.

As the FAA filed it

INCIDENT REPORTED TO FSDO BY AIRPORT MANAGER. INCIDENT OCCURRED THE PREVIOUS EVENING. TRIED CONTACTING ^PRIVACY DATA OMITTED^ TO NO AVAIL. SENT REGISTERED MAIL TO ^PRIVACY DATA OMITTED^ RECEIVED REPLY FROM ^PRIVACY DATA OMITTED^ STATING THE AIRCRAFT HAD A PROP STRIKE WITH NO OTHER OPERATIONAL DAMAGE. CITING 49 CFR PART 830.2, HE DID NOT BELIEVE IT MERITED FURTHER INVESTIGATION. SENT RESPONSE TO LAWYER CITING 49 CFR § 44709, ALLOWS FOR THE ADMINISTREATOR TO REINSPECT AT ANY TIME A CIVIL AIRCRAFT. AFTER THIS NOTICE THE AIRCRAFT WAS MADE AVAILABLE FOR INSPECTION. PILOT IN COMMAND REPORTED THAT AFTER ABOUT THIRTY MINUTES OF PATTERN WORK, CREW EXECUTED A STANDARD PATTERN TOUCH AND GO LANDING. WHILE ON CROSSWING AND AT PATTERN ALTITUDE PIC INITIATED A SIMULATED ENGINE FAILURE. ONCE INITIATED THIS CALLED FOR A RETURN TO THE AIRPORT TO LAND IN THE OPPOSITE DIRECTION OF THE TOUCH AND GO. PIC REPORTED THAT WHILE THE CHECKLIST WAS OUT AND IN USE THE CREW FAILED TO LOWER THE GEAR. PIC ATTRIBUTED THIS TO BEING DISTRACTED BY A DISCUSSION ON DIVE BRAKE DEPLOYMENT AND PROPELLER SETTINGS. FIRST INDICATION OF THE GEAR UP CONDITION WAS THE BELLY SCRAPING ON THE RUNWAY. THE PROPELLER STRUCK THE RUNWAY SHORTLY THEREAFTER. PIC REPORTED THE AIRCRAFT WAS CONTROLABLE TO A STOP. DAMAGE OBSERVED TO THE PROPELLER AND THE NONSTRUCTURAL BELLY OF THE AIRCRAFT. DAMAGE IS NOT SUBSTANTIAL BY DEFINITION.

Other reports on N86BZ · 1

Matched to the same aircraft by N-number and date.