Piper PA-28-181 accident near Block Island, Rhode Island, July 30, 2025
On July 30, 2025 at about 4:10 pm local time, a 1996 Piper PA-28-181, registered N961DA, was substantially damaged in an accident during landing (landing roll) near Block Island, Rhode Island (Block Island State Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed, 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 30, 2025 · about 4:10 pm local time
- Place
- Block Island, Rhode Island · Block Island State Airport · map
- Type
- Accident
- Injuries
- 1 person was killed, 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-181, built 1996 · all PA-28-181s on the register
- Registration
- N961DA · registry record · serial 2843034
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
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 major components 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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Landing area overshoot during landing (flare/touchdown)
- Collision during takeoff/land during landing (landing roll) defining event
The aircraft
- Airframe total time: 3,743.3 hours
- Last inspection: annual inspection, January 21, 2025
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Operator: Condair Flyers INC
The flight
- Departed from: ALB Albany NY at 2:50 pm
- Flight plan: VFR
- Runway 10, 2,502 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 230° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 86°F (30°C), dew point 68°F (20°C)
- Altimeter: 30.00 inHg
- Observation at 11:56 am from BID
Weather report (METAR): KBID 301556Z AUTO 23007KT 10SM CLR 30/20 A3000 RMK AO2 SLP159 T03000200 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
