FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA309 · Cessna A185F

22 Aug 2025 · Bangor, ME, United States

Cessna A185F · Accident: loss of control on ground during landing

From Goose Bay Airport (CYYR) to an unrecorded destination

Report a problem

Event

NTSB case
ERA25FA309
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna A185F

Aircraft type
Cessna 185
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N714HE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Goose Bay Airport (CYYR), Goose BayTo not recorded
Aircraft age
About 43 years (built 1982)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On August 22, 2025, at 1321 eastern daylight time, a Cessna A185F, N714HE, was substantially damaged when it was involved in an accident near Bangor, Maine. The pilot was fatally injured. The flight was being conducted as a 14 Code of Federal Regulations Part 91 ferry flight. According to the airplane owner, the pilot was ferrying the airplane from Europe to the United States. The final destination was Rutland, Vermont. A preliminary review of radar data and air traffic control communications revealed the pilot departed Goose Bay Airport (CYYR), Newfoundland - Labrador, Canada, at 0801, and flew direct to Bangor International Airport (BGR), Bangor, Maine, to clear customs. The pilot was provided with the airport’s current automated terminal information service (ATIS) information and cleared for a visual approach to runway 33. While on short final, the pilot asked the control tower for a “wind check.” A controller responded, “…wind 020 at 14 gusting to 19.” A Federal Aviation Administration (FAA) employee was driving south on the airport perimeter road located west of the runway when he saw the airplane attempting to land. He said, “While the plane was landing, I noticed his left wing getting very close to the pavement. He seemed to have tried to correct himself, however there was a crosswind blowing East.” The witness said the airplane veered left toward the precision approach path indicator (PAPI) lights and struck one of the lights. The airplane then “picked back up into the air” and flew “sideways in an arcing motion” directly toward him. The witness ducked down and heard the airplane hit the airport perimeter fence. When he looked up, he saw the airplane impact the ground and cartwheel. A review of cell phone and airport surveillance video revealed that as the airplane touched down on the runway, it bounced and began to ground loop to the left. The airplane’s left wing contacted the ground, and the airplane struck a PAPI light located on the left side of the runway. The airplane became airborne again and entered a steep left bank/turn, struck the airport perimeter fence, and impacted a field west of the runway. There was no postimpact fire. The pilot was an Italian citizen and held several Italian flight certificates. He also held a Federal Aviation Administration (FAA) foreign-based private pilot certificate for airplane single-engine land. His last FAA second-class medical certificate was issued on May 31, 2024. At that time, he reported a total of 2, 200 flight hours. At 1253, the weather conditions at BGR were reported as wind from 350 degrees at 10 knots gusting to 18 knots, visibility 10 miles, with scattered clouds at 7,000 ft. At 1339, the weather conditions at BGR were reported as wind from 010 degrees at 9 knots gusting to 19 knots, 10 miles visibility, with scattered clouds at 7,000 ft. The airplane wreckage was recovered and taken to a secure facility for further examination by the NTSB.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25FA309
Event ID
20250822200839
Case number
ERA25FA309
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: efe8ff51bacff58d5e09dcc1d9f3dfa27ae388f1c4e7f2caa5fa219b2ddabcf3; retrieved 2026-09-15T09:08:11.560Z.