Piper PA-28-161 N266ND

Summary

On 25 January 2021 at about 01:00 local time, a Piper PA-28-161 registered N266ND, operated by 2Fly Airborne, was involved in an accident near Boynton Beach, Florida, United States. One person was on board and one died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

25 January 2021 at 01:00

Classification

Accident

Location

Boynton Beach, Florida, United States

Nearest airport

Palm Beach County Park (LNA)

Coordinates

26.5412, -80.0371

Aircraft

Piper PA-28-161

Registration

N266ND

Category

Airplane

Year built

2000

Engines

1

Operator

2Fly Airborne

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Lantana → Merritt Island

Aircraft damage

Substantial

Weather

VMC

Light

Night

NTSB number

ERA21LA111

1 person died.

The pilot’s controlled flight into the ocean at night due to his unrecognized spatial disorientation. Contributing to the accident was the pilot’s distraction with the tuning of his transponder while maneuvering over an area with reduced visual references.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

While in cruise flight about 1,000 ft on a southbound heading over land in night visual meteorological conditions, the pilot requested flight following services and routing to the north “along the shoreline.” Air traffic control approved the request, issued the altimeter setting, and instructed the pilot to proceed offshore and “follow the shoreline northbound at or below 500 feet.” The pilot acknowledged the instructions and repeated the altimeter setting as the airplane began a descending left turn to the east. The target identified as the accident airplane continued an eastbound descent on a heading about perpendicular to the shoreline when the controller assigned the airplane a new transponder code. When the pilot acknowledged the transponder code instructions, the airplane was at 300 ft and descending and displayed a transponder code one digit off that which was assigned. At that time, the airplane was crossing the beach at 225 ft and descending. Once over water, the airplane’s track depicted a shallow, descending left turn. Soon after, radar contact was lost and there were no further communications with the airplane. Onboard video revealed that the descent was initiated by multiple reductions in engine rpm as the airplane turned to the east, consistent with the controller’s instructions to fly offshore and continue north below 500 ft; however, no sounds consistent with an increase in engine rpm to arrest the descent occurred after the airplane began tracking toward the ocean, nor in the final moments of flight as the airplane initiated a turn toward the north well below 500 ft. Given the dark nighttime conditions, the pilot’s lack of instrument experience likely focused his attention outside the aircraft. In a low-wing airplane, cultural/ambient lighting on the ground ahead of the airplane would have provided some cues of both altitude and attitude; however, the availability of those cues would have rapidly decreased as the airplane neared the shoreline. The circumstances of this accident suggest that the pilot over-relied on outside references and did not effectively reference the altimeter. The controller’s instructions to reset the transponder code about the same time the airplane was descending through 500 ft, although routine, likely served as an operational distraction to a pilot with his limited experience. His efforts to reset the transponder likely further diverted his attention away from the altimeter, and the pilot allowed the airplane to descend into the water.

Quoted verbatim from the NTSB record.