# Incident 20160413024769I: Dehate Michael L LANCAIR IV, April 13, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 13, 2016, 09:05 local time
- Airport: Phoenix-Mesa Gateway
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Aircraft: N144MD, registered now (https://openairdocs.org/aircraft/N144MD) (OpenAirDocs)
- Registry model: Dehate Michael L LANCAIR IV (registry code 05626QK, https://openairdocs.org/model/dehate-michael-l-lancair-iv) (OpenAirDocs)
- Reported make and model: DEHATE MICHAEL L LANCAIR IV
- Reported engine: CONT MOTOR IO-550-G
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 900 total, 150 in this make and model, 3 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160413024769I

## Narrative

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

AIRCRAFT WAS BEING FLOWN ON FIRST FLIGHT AFTER MAINTENANCE. PILOT REPORTED HE HAD TAKEN OFF FROM FFZ BOUND FOR TUS AND HAD CLEARED THE TRAFFIC PATTERN AREA. AS HE WAS ATTEMPTING TO CONTACT PHX FOR FLIGHT FOLLOWING HIS ENGINE BEGAN TO SURGE. HE NOTED THAT THE MANIFOLD PRESSURE HAD DROPPED FROM 29-30 IN MAP TO APROX 17 IN MAP. WHEN PHX ATC CALLED HIM BACK HE INFORMED THEM THAT HIS ENGINE WAS GIVING HIM PROBLEMS. SINCE HE WAS ABEAM IWA AT THE TIME HE ASKED TO BE DIVERTED TO THE NEAREST AIRPORT WHICH WAS IWA FOR A PRECAUTIONARY LANDING. HE ALSO ASKED TO BE GIVEN THE TOWER FREQUENCY AS HE DID NOT HAVE TIME TO LOOK THE INFO UP. PHX GAVE HIM IWA TOWER FREQUENCY AND WHEN HE CHECKED IN IWA CLEARED HIM TO LAND ON RWY 30. THE FIRE TRUCKS WERE DEPLOYED AND THE PILOT LANDED WITHOUT FURTHER INCIDENT. WHILE HE WAS ON BASE TO FINAL THE ENGINE REGAINED POWER AFTER SURGING SEVERAL TIMES AND THE PILOT NOTED THERE WAS NO FURTHER SURGING AFTER THAT POINT.

THE AIRCRAFT WAS ABLE TO TAXI TO PARKING ON ITS OWN POWER AND FIRE DEPARTMENT DETERMINED THERE WAS NO SAFETY ISSUES WITH THE AIRCRAFT AND DEPARTED.

THE PILOT CONTACTED THE MAINTENANCE FACILITY THAT HAD PERFORMED WORK ON THE AIRCRAFT. THE SUGGESTED THAT THERE MIGHT BE WATER IN THE FUEL AS THE AIRCRAFT HAD SAT OUTSIDE THE NIGHT BEFORE AND A RAINSTORM HAD MOVED THRU THE AREA. THEY SUGGESTED HE DRAIN THE SUMPS AND TRY RUNNING THE ENGINE AGAIN.

THE PILOT DID REMOVE SEVERAL CUPS OF FUEL FROM THE FUEL SUMPS AND HE RAN THE ENGINE UP 2 TIMES WITH NO DEFECTS NOTED. HE THEN DECIDED THAT HE WOULD FINISH HIS FLIGHT HOME TO RYAN FIELD AS THE DAY HAD WARMED UP CONSIDERABLY. HE FLEW THE AIRCRAFT TO RYAN AND ON SEVERAL FLIGHTS SUBSEQUENT TO THE FUEL FLOW ISSUE AND THE ENGINE HAS CONTINUED TO RUN NORMALLY SINCE.

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.