ERA17LA014 · Cessna 525 B
Cessna 525 B · Accident: runway excursion during landing
From Allegheny County Airport (AGC) to North Central State Airport (SFZ)
Event
- NTSB case
- ERA17LA014
- 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
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
- Instrument Meteorological Cond
Cessna 525 B
- Aircraft type
- Cessna 525
- 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
- N518AR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Allegheny County Airport (AGC), Pittsburg, PATo North Central State Airport (SFZ), Pawtucket, RI
- Aircraft age
- About 2 years (built 2014)
- 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
- Runway excursion
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tower/antenna (incl guy wires)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA014
- Event ID
- 20161013X35806
- Case number
- ERA17LA014
- 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. 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: efdb32ab314574726b6dd7b29ad1f172757d9dd743c23f2c76271db96da6308a; retrieved 2026-09-16T04:23:44.861Z.