Piper PA-32R-300 N47630 accident near White Plains, New York

Sep 23, 2025 · NTSB number ERA25LA363 · Final report

Probable cause

The pilot’s failure to maintain proper glidepath during a night visual approach, which resulted in a collision with the runway lighting system. Contributing to the outcome was the pilot’s momentary disorientation due to glare from the runway approach lighting system.

NTSB analysis

The pilot was landing the airplane in night visual meteorological conditions. The pilot reported that during the turn to final approach, the tower air traffic controller cleared a large transport-category airplane for departure. To avoid potential wake turbulence, the pilot adjusted the planned touchdown point to be before the expected rotation point of the departing airplane. While reconfiguring for the new touchdown point, the pilot encountered glare from the runway approach lighting system, which temporarily degraded his night vision and momentary disoriented him. The airplane then began to sink and as the pilot was making corrective control inputs he felt a “bump,” after which he landed uneventfully. Subsequent examination of the runway’s approach lighting system and the airplane revealed that the airplane had struck the runway lighting system before touchdown, resulting in substantial damage to the root sections of both wings and the right side of the stabilator. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Text from the NTSB. Open the NTSB docket for ERA25LA363 for the full record.

Event

Date
Sep 23, 2025
Type
Accident
Place
White Plains, New York
Nearest airport
Westchester County (HPN)
Highest injury
None
Weather
Visual (VMC)
Light
Night

Piper PA-32R-300

N-number
N47630
Category
Airplane
Year built
1977
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Personal

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.