FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18LA204 · Progressive Aerodyne SEAREY

29 Jul 2018 · Haverhill, NH, United States Possible conflict

Progressive Aerodyne SEAREY · Accident: loss of control in flight while maneuvering

From Haverhill, NH to Haverhill, NH

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA18LA204
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
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
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

Progressive Aerodyne SEAREY

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
N221EZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Haverhill, NHTo Haverhill, NH
Aircraft age
About 12 years (built 2006)
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
Maneuvering · low-altitude flying
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 in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot took off in the experimental, amateur-built amphibious airplane from a river, which was about 100 ft wide and lined with trees on both sides, and initiated a right 180° turn. He then made a left teardrop turn about 50 ft above ground level over a flat cornfield to make a 45° re-entry to land back on the river. When the airplane crossed over the river's shoreline, the pilot attempted to turn left and line up with the river; however, according to the pilot, the control stick would not move past the vertical position. He added power, but the airplane was unable to climb above trees on the opposite side of the river. The airplane collided with the trees and descended into the water. Postaccident examination of the airplane revealed both wings had been removed during recovery, but the flight controls moved freely when manually manipulated. The pilot said the airplane's automatic dependent surveillance-broadcast (ADS-B) component, which was attached to the control panel via a suction cup, may have come loose during the flight and become caught under the flight control assembly, thus jamming the flight controls. He demonstrated how an object could get caught under the controls; however, neither he nor the passenger could confirm that this happened on the accident flight, and examination of the ADS-B component did not reveal any physical damage. The pilot said that he would normally climb above the surrounding terrain before coming back to land; however, during this flight, he did not give himself an "out" in case of an emergency. His decision to maneuver the airplane below surrounding terrain in a confined area left insufficient altitude to troubleshoot a perceived flight control issue, and he was unable to remain clear of trees.

Probable cause

The pilot's failure to maintain clearance from trees while maneuvering the airplane at a very low altitude in a confined area while attempting to land on a river.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18LA204
Event ID
20180729X60702
Case number
ERA18LA204
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. 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: 9f7a714cc97524fdc1ef66e801a524199b033764499348a5eeb04ac137f1145b; retrieved 2026-09-16T08:01:26.945Z.