The U.S. aircraft register, updated daily
Accidents · NTSB ERA17LA014 · Final report

Cessna 525 accident near Pawtucket, Rhode Island, October 13, 2016

On October 13, 2016 at about 2:00 pm local time, a 2014 Cessna 525, registered N518AR, was substantially damaged in an accident during landing (landing roll) near Pawtucket, Rhode Island (North Central State airport). It was a business flight under general aviation rules (Part 91). No one was hurt; 6 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The flight crew's failure to maintain an appropriate approach speed and obtain an appropriate touchdown point on the runway, which resulted in a runway overrun.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 13, 2016 · about 2:00 pm local time
Place
Pawtucket, Rhode Island · North Central State · map
Type
Accident
Injuries
No one was hurt; 6 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cessna 525 B, built 2014 · all 525s on the register
Registration
N518AR · registry record · serial 525B0412
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

After an uneventful instrument flight rules flight, the flight crew of the turbofan-powered airplane conducted an instrument approach to the 5,000-ft-long runway. The commercial pilot, who was the pilot flying, reported that the airplane's airspeed during the approach was "a little too fast" at 130 to 135 knots. A witness watched as the airplane flew beyond the runway touchdown zone and touched down on the runway with about 2,000 ft remaining. The flying pilot stated that he then "slammed on the brakes," and the airplane's antiskid system engaged. The airplane subsequently departed the end of the runway, struck several localizer antennae, and came to rest in trees and bushes beyond the departure end of the runway. Although the flying pilot reported that the brakes felt "a little spongy" during the landing, the nonflying pilot stated that, during the landing, both pilots were applying the brakes and that it appeared that the brakes and the antiskid system were working. Postaccident examination of the brakes and brake lines showed no evidence of any preimpact anomalies, and intermittent tire skid marks near the end of the runway appeared consistent with braking and operation of the airplane's antiskid system. Postaccident calculations showed that the airplane's approach speed should have been about 114 knots; the airplane's actual approach speed was more than 130 knots. Additionally, the airplane's calculated landing distance was 2,650 ft; however, there was only about 2,000 ft of runway available when the airplane touched down. Given this information, it is likely that the flight crew approached the runway at an excessive speed and touched down with insufficient runway remaining to stop the airplane and prevent a runway overrun.

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

  1. Runway excursion during landing (landing roll) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • Environmental issues › Physical environment › Object/animal/substance › Tower/antenna (incl guy wires) › Contributed to outcome

Pilot

  • Certificate: commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 8,000 hours in all; 400 in this make and model; 8,000 as pilot in command
  • Last flight review: November 9, 2015
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot, military, private
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 6,000 hours in all; 700 in this make and model; 50 in the last 90 days; 30 in the last 30 days; 2,500 as pilot in command
  • Last flight review: July 1, 2016
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 748 hours
  • Last inspection: continuous airworthiness programme, October 7, 2016
  • Maximum gross weight: 13,750 lb
  • Seats: 8
  • Landing gear: retractable
  • Engine 1: Williams FJ44-3A (turbofan); 748 hours total
  • Engine 2: Williams FJ44-3A (turbofan); 748 hours total

The flight

  • Departed from: AGC Pittsburg PA at 1:00 pm
  • Destination: SFZ Pawtucket RI
  • Flight plan: IFR
  • Runway 05, 5,000 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 3 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 59°F (15°C), dew point 57°F (14°C)
  • Altimeter: 30.09 inHg
  • Observation at 2:23 pm from KSFZ, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers4

Documents from the investigation the NTSB's docket: the evidence folder behind the report

6 documents, released by the NTSB on November 25, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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.