NTSB CAROL · Event
Event ERA25FA280
Registry · N961DA
FAA Aircraft Registry record.
Make / Model
PIPER PA-28-181
Year of manufacture
1996 · 29 years old at event
Engine
LYCOMING O&VO-360 SER (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19960405
ADS-B equipped
Yes — Mode-S AD6029
Registrant of record
CONDAIR FLYERS INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Factual narrative
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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2025_ERA25FA280.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗