FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA280 · Piper PA-28-181

30 Jul 2025 · Block Island, RI, United States

Condair Flyers Piper PA-28-181 · Accident: collision during takeoff/landing

From Albany International Airport (ALB) to an unrecorded destination

Report a problem

Event

NTSB case
ERA25FA280
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-181

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N961DA
Onboard fatalities
Unknown
Route
From Albany International Airport (ALB), Albany, NYTo not recorded
Aircraft age
About 29 years (built 1996)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB 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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25FA280
Event ID
20250730200669
Case number
ERA25FA280
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 991386f7fc3bfdc176222f8a9e14a9548ac69aeaa2aa46d1cc7e3ca00e53b367; retrieved 2026-09-15T09:07:27.935Z.