20000215041391A

Accident · Substantial damage

FAA accident report · Piper PA-28-236 · Sandusky, OH · February 15, 2000

Date
February 15, 2000 · 14:25 local
Place
Sandusky, OH
Airport
Griffing Sandusky Airport
Phase of flight
Normal Cruise
Operating rules
General operating rules (Part 91)
Collision
Midair collision, first aircraft
Damage
Substantial damage
Aircraft
N8264G
NTSB investigation
NTSBNYC00LA081
Reported as
Piper PA28236
Pilot’s flight hours
3,487 total400 in this make and model75 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.

(-23) Aircraft N8264G, Piper dakota, was level cruise flight at 3700' MSL heading north. Purpose of flight was engine break-in after maintenance. The second aircraft, N1742V, Cessna 172, was on a pleasure flight, had just departed Sandusky (sky) airport was climbing to altitude for a return flight to galion (gqq) airport heading 180. The dakota felt a jolt, thought he had a bird strike and headed eastbound to his home airport. He had no problem holding altitude, returned to the airport and landed on the active runway without incident.

As the FAA filed it

(-23) AIRCRAFT N8264G, PIPER DAKOTA, WAS LEVEL CRUISE FLIGHT AT 3700' MSL HEADING NORTH. PURPOSE OF FLIGHT WAS ENGINE BREAK-IN AFTER MAINTENANCE. THE SECOND AIRCRAFT, N1742V, CESSNA 172, WAS ON A PLEASURE FLIGHT, HAD JUST DEPARTED SANDUSKY (SKY) AIRPORT WAS CLIMBING TO ALTITUDE FOR A RETURN FLIGHT TO GALION (GQQ) AIRPORT HEADING 180. THE DAKOTA FELT A JOLT, THOUGHT HE HAD A BIRD STRIKE AND HEADED EASTBOUND TO HIS HOME AIRPORT. HE HAD NO PROBLEM HOLDING ALTITUDE, RETURNED TO THE AIRPORT AND LANDED ON THE ACTIVE RUNWAY WITHOUT INCIDENT.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other aircraft in the event · 1

Each aircraft in a collision has its own report.