Summary
On July 26, 2012, a Bayliss Milton A III X-AIR (N8076E) was involved in an incident near Houlton, ME. All 1 person aboard were uninjured. The aircraft sustained substantial damage.
The National Transportation Safety Board determined the probable cause of this incident to be: The pilot's failure to maintain directional control during the landing flare in a gusting crosswind, which resulted in a runway excursion.
The pilot stated he departed on a visual flight rules local flight. He returned to the airport and entered closed traffic for landing. During the landing flare, he lost directional control of the airplane due to a cross wind. The aircraft departed the left side of the runway and collided with the ground. During the accident sequence, the airplane incurred substantial damage to the fuselage. Wind gusts of 14 knots were reported at the time of the accident. The pilot reported there were no mechanical malfunctions or failures that would have precluded normal operations.
This incident is documented in NTSB report ERA12CA485. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N8076E.
Accident Details
Probable Cause and Findings
The pilot's failure to maintain directional control during the landing flare in a gusting crosswind, which resulted in a runway excursion.
Aircraft Information
Registered Owner (Historical)
Analysis
The pilot stated he departed on a visual flight rules local flight. He returned to the airport and entered closed traffic for landing. During the landing flare, he lost directional control of the airplane due to a cross wind. The aircraft departed the left side of the runway and collided with the ground. During the accident sequence, the airplane incurred substantial damage to the fuselage. Wind gusts of 14 knots were reported at the time of the accident. The pilot reported there were no mechanical malfunctions or failures that would have precluded normal operations.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA12CA485