FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26FA216 · Piper PA-36-300

11 Jun 2026 · Henderson, NE, United States

Boardman Air Services Piper PA-36-300 · Accident while maneuvering

Report a problem

Event

NTSB case
WPR26FA216
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
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

Piper PA-36-300

Aircraft type
Piper PA-36
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
N57846
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 49 years (built 1977)
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 137: Agricultural
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
Unknown or undetermined
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 June 11, 2026, at 2103 central daylight time, a Piper PA-36-300, N57846, was substantially damaged when it impacted a rotating beacon tower and terrain near Henderson, Nebraska. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 137 agricultural flight. According to the agricultural application operator, the pilot was performing a mosquito abatement aerial application flight at dusk. Review of security surveillance video footage from a camera located about 421 ft southeast of an unlit tower, showed that the airplane was flying from east to west and collided with the approximately 50 ft tall tower. At the time of the collision, the video showed the airplane was traveling toward the setting sun. Recorded Spidertrack data showed that the flight departed at 2052, with a total flight duration of 11 minutes. Preliminary ADS-B data indicated that the airplane was on a heading of about 268° magnetic at an altitude of 40 ft above ground level when the collision occurred. According to the United States Naval Observatory Astronomical Applications Department, at 2100 the position of the sun was 0.2° above the horizon, on an azimuth of 301.6° magnetic. The accident site was located in a bean field about 280 ft west of the unlit tower. The first identified point of contact with the ground was a series of ground scars located about 272 ft from the tower, on a heading of 275° magnetic. The airplane came to rest about 57 ft west of the initial point of terrain impact, on a heading of 090° magnetic. About 4 ft of the inboard right wing and flap remained attached at the fuselage, and the remainder of the right wing came to rest about 20 ft south of the fuselage. Witness marks on the inboard section of right wing showed concave depressions at the leading edge about 12 inches from the wing root. The main wreckage consisted of the fuselage, empennage, left wing, engine and the propeller. The fuselage sustained impact damage and the cockpit structure was mostly intact with deformation observed to the floor section in downward displacement. The left wing was partially separated from the fuselage with impact damage sustained to the wing root, with the flap and aileron present. The vertical stabilizer, rudder, left side vertical stabilizer and elevator remained attached and were unremarkable. The right side horizontal stabilizer and elevator remained attached and sustained impact damage. The engine was partially separated from the forward fuselage, and all four engine mounts were fractured. The two blade constant speed propeller remained attached to the crankshaft propeller flange. Both propeller blades remained attached to the propeller hub, with one of the blades bent forward and the outboard 11 inches was fracture separated and located about 75 ft south of the tower and perpendicular to the direction flight. The opposite propeller blade was bent aft about 80° opposite the direction of rotation and exhibited gouging on the leading edge.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR26FA216
Event ID
20260612203167
Case number
WPR26FA216
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2026-06-12.
  • API snapshot SHA-256: db03e196981aa055db57cf406f3da8165b16844883c83df4e24015668814b36a; retrieved 2026-09-15T09:16:38.312Z.