# Accident 20180719014539A: Michael S Toomey QUICKIE, Zanesville, OH, July 19, 2018

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 19, 2018, 15:00 local time
- Place: Zanesville, OH
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 39.9886° N, 81.8847° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.9886&lon=-81.8847&mi=10
- Aircraft: N23JH, registered now (https://openairdocs.org/aircraft/N23JH) (OpenAirDocs)
- Registry model: Michael S Toomey QUICKIE (registry code 05632S9, https://openairdocs.org/model/michael-s-toomey-quickie) (OpenAirDocs)
- Registry engine: Onan ALL MDLS A/B (registry code 47850, https://openairdocs.org/engine/onan-all-mdls-a-b) (OpenAirDocs)
- Reported make and model: MICHAEL S TOOMEY QUICKIE
- Reported engine: ONAN ALL MDLS A/B
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 600 total, 40 in this make and model, 48 in the last 90 days
- NTSB investigation: [NTSB CEN18LA284](https://openairdocs.org/ntsb/CEN18LA284) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180719014539A

## Narrative

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

AIRCRAFT OWNER DEPARTED BUTLER COUNTY AIRPORT (KHAO) NEAR CINCINNATI OHIO AND LANDED IN ZANESVILLE OHIO (KZZV) WITH NO ISSUES.  PILOT THEN TOOK OFF FROM ZZV WITH ANOTHER AIRCRAFT FLYING NEARBY TO TAKE AERIAL PHOTOS OF HIS AIRCRAFT.  AFTER PHOTO SHOOT WAS COMPLETE THE PILOT OF THE ACCIDENT AIRCRAFT GAVE A "RUDDER WAG" TO SIGNIFY HE WAS GOING TO HEAD BACK TO ZZV.  AT THAT MOMENT THE ENGINE EXPERIENCED A SUDDEN LOSS OF POWER.  THE PILOT REPORTED THE FOLLOWING:  "IMMEDIATELY AFTER (THE RUDDER WAG), MY POWER SETTING DROPPED BY OVER 1000RPM (3700RPM  2600RPM) AND BEGAN PULLING WITH ABOUT TWICE THE FUEL (1.8GPH  3.0GPH). I WAS ABLE TO MAINTAIN MY CURRENT AIRSPEED (ABOUT 80MPH) AND ALTITUDE (ABOUT 1000FT AGL) SO I ANNOUNCED THAT I WAS HAVING ENGINE TROUBLE AND WAS PLANNING A STRAIT IN FOR RUNWAY 16. WHEN THIS STARTED, I WAS APPROXIMATELY 4 MILES NORTH OF THE AIRPORT AND NOTICED INTERSTATE 70 CLOSE TO THE AIRPORT THAT I PLANNED TO USE IF I COULD NOT MAKE THE FIELD. A MOMENT AFTER ANNOUNCING MY INTENTIONS, MY RPM SETTING BEGAN TO DROP EVEN FURTHER. LOSING A STEADY 20-RPM PER SECOND I KNEW I WOULD NOT BE ABLE TO MAKE THE AIRPORT. SEEING A NEIGHBORHOOD BETWEEN I-70 AND MY CURRENT POSITION - NOW ABOUT 3 MILES FROM THE AIRPORT - I LOOKED RIGHT, SAW A FOREST AND LOOKED LEFT TO SEE A DOGLEG OF A ROAD POINTED INTO THE WIND WITH FIELDS BEYOND IT. SEEING THIS AS MY BEST OPTION, I TOLD ^PRIVACY DATA OMITTED^ (TRAIL PLANE PILOT)MY INTENTIONS OVER THE ZANESVILLE UNICOM FREQUENCY AND BEGAN A DESCENDING RIGHT TURN DOWN TO THE ROAD. NARROWLY MISSING SOME TREES AND NOT SPOTTING ANY TRAFFIC, I LINED UP FOR THE ROAD WITH TOO MUCH ENERGY AND ALTHOUGH INCHES FROM THE GROUND, KNEW I COULD NOT STOP IN TIME. "  THE PILOT HAD TOO MUCH ENERGY TO SAFELY LAND ON THE ROAD AND OPTED FOR THE ADJACENT CORN FIELD.  HE HIT THE CORN AT APPROXIMATELY 45 MPH AND CAME TO REST UPSIDE DOWN IN THE CORN.  HE DID NOT SUSTAIN ANY MAJOR INJURIES BUT HAD TO WAIT ABOUT 1 HOUR FOR FIRST RESPONDERS TO FLIP[THE AIRCRAFT OFF OF HIM TO FREE HIM FROM THE WRECKAGE. THE ENGINE NEVER FULLY STOPPED RUNNING BUT WAS NOT CREATING ENOUGH POWER TO SUSTAIN FLIGHT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN18LA284](https://openairdocs.org/ntsb/CEN18LA284), Jul 19, 2018: Toomey Quickie (N23JH), Zanesville, OH, substantial damage. Probable cause: The failure of the exhaust manifold and a loose mixture screw, which resulted in a partial loss of engine power.

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.