# NTSB ERA25FA280: Piper PA-28-181, N961DA, Block Island, RI, July 30, 2025 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: July 30, 2025, 12:10 local (16:10 UTC) - Place: Block Island, RI · In trees 500 ft from runway - Coordinates: 41.168792, -71.570874 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.1688&lon=-71.5709&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Fatal - Injuries: 1 fatal, 1 serious, 1 minor - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: Piper Aircraft, Inc., FAA FSDO, Lycoming Engines - NTSB case key (mKey): 200669 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25FA280 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200669/pdf - Page: https://openairdocs.org/ntsb/ERA25FA280 ## Preliminary report On July 30, 2025, about 1210 eastern daylight time, a Piper PA-28-181, N961DA, was substantially damaged when it was involved in an accident near Block Island, Rhode Island. The pilot sustained serious injuries, one passenger received minor injuries, and one passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The flight departed Albany International Airport (ALB), Albany, New York, about 1050, enroute to Block Island State Airport (BID), Block Island, Rhode Island. The pilot reported that the purpose of the flight was to fly with two passengers to BID for lunch. About 20 nautical miles (nm) from BID, the pilot began his descent and obtained the automated weather information. At 1156, the automated weather observation at BID recorded wind from 230° at 7 knots, which corresponded to a tailwind and crosswind component for landing on runway 10. The pilot reported that he entered the left downwind leg of the traffic pattern for runway 10, and on the final approach leg of the traffic pattern, he observed an airplane departing runway 28 and initiated a go-around. During a second approach, he turned from the downwind leg to final approach leg of the traffic pattern too close to the runway and initiated another go-around. After a third approach to runway 10, the airplane touched down with full flaps about 1,500 ft down the 2,500-ft-long runway. As the pilot applied the brakes, the airplane’s right wing lifted due to a gust of wind. There was insufficient runway remaining for a go-around, the airplane overran the runway and impacted trees. Preliminary ADS-B data indicated the airplane crossed the runway threshold at 174 ft altitude and 104 knots groundspeed, touched down at 83 knots, and exited the runway at 73 knots. The final recorded point was about 55 ft from the end of the overrun area at 70 knots. Preliminary air traffic control (ATC) audio indicated the pilot was receiving visual flight rules (VFR) advisories from Providence Terminal Radar Approach Control (TRACON). About 20 nm from BID, ATC advised that radar services were terminated, to “squawk” VFR, and frequency change was approved. Although the pilot acknowledged, he remained on the Providence TRACON frequency and reported his position in the BID traffic pattern for two of three approaches. ATC advised him several times that he was transmitting on the incorrect frequency and provided the correct advisory frequency. The overrun area of runway 10 was a flat grassy surface about 243 ft long at an elevation of about 102 ft mean sea level (msl). Three linear tire impressions, consistent with landing gear, were observed about 25 ft from the end of the overrun area on a 099° magnetic heading. No tire friction marks were observed on the runway or overrun before that point. The airplane came to rest inverted on a 209° magnetic heading about 640 ft east of the departure end of runway 10 at an elevation of about 40 ft msl. All majorcomponents of the airplane were located at the accident site. The first identified point of impact was a tree canopy about 50 ft above ground level and 467 ft from the departure end of the runway. Several tree branches exhibited angular cuts with black transfer marks. A ground impression containing the separated nose landing gear was located about 128 ft from the first impact point and 45 ft from the main wreckage. The wreckage path was oriented on a 096° magnetic heading and about 173 ft long. Vegetation staining consistent with fuel exposure was observed along the debris path. Examination of the airframe and engine revealed that flight control continuity was established from the cockpit to all the flight control surfaces, and the flap position was noted at 40°. The empennage exhibited impact damage and the stabilator trim was noted in a partial nose-down trim setting. Both wings exhibited impact damage, and the left wing was partially separated from the fuselage. Both fuel tanks were breached from impact forces. Fuel system continuity was established, and fuel consistent in color and odor to 100LL aviation gasoline was observed in the system. The engine remained attached to the engine mount. Both magnetos produced spark from their ignition towers during hand rotation of their attached drive gears. Crankshaft and valvetrain continuity were established, and compression and suction were obtained on all four cylinders. The propeller remained attached to the engine with chordwise abrasion and leading-edge damage noted to both propeller blades. The wreckage was retained for further examination. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Piper PA-28-181, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=7102807), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Piper PA-28-181, 9 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=7102807), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Aircraft - Registration: [N961DA](https://openairdocs.org/aircraft/N961DA), registered now, S/N 2843034, built 1996 (OpenAirDocs) - Reported make and model: PIPER PA-28-181 - Registry model: [Piper PA-28-181](https://openairdocs.org/model/piper-pa-28-181) (registry code 7102807) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2843034 - Year built: 1996 - Airframe hours: 3743.3 - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Condair Flyers Inc - Registered owner: Condair Flyers Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 21, 2025 - Departed: ALB, Albany, NY - Destination: Same as departure - Flight plan: VFR - Airport: BID, Block Island State Airport, runway 10, 2,502 × 100 ft, asphalt - Equipment: ADS-B, Electronic primary flight display, Stall warning system ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 86 °F, dew point 68 °F - Altimeter: 30.00 inHg - Observed at: BID - METAR: KBID 301556Z AUTO 23007KT 10SM CLR 30/20 A3000 RMK AO2 SLP159 T03000200 $ ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20250730009509A](https://openairdocs.org/incident/20250730009509A), Jul 30, 2025: Piper PA-28-181, Block Island, RI, Destroyed, 1 fatal. At approximately 1228 local time on Wednesday, July 30, 2025 a single-engine aircraft crashed in the trees approximately 500 feet beyond the landing runway's… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.