NTSB CAROL · Event
Event ERA15LA380
Registry · N622PG
FAA Aircraft Registry record.
Make / Model
CESSNA 550
Year of manufacture
1978 · 37 years old at event
Engine
P&W CANADA JT15D-4
Seats / Engines
8 seats · 2 engines
Last airworthiness date
19970121
ADS-B equipped
Yes — Mode-S A81EF7
Registrant of record
CAPITAL CRAFT LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to attain the proper touchdown point and to adequately slow the airplane within the available runway, which resulted in a runway overrun.
Factual narrative
On September 27, 2015, about 1906 eastern daylight time, a privately owned and operated Cessna 550, N622PG, was substantially damaged during a runway excursion after landing at the Sarasota Bradenton International Airport (SRQ), Sarasota, Florida. The airline transport pilot and the passenger sustained minor injuries. Visual meteorological conditions prevailed and an instrument flight rules flight plan was filed for the personal flight, which was conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight departed Boca Raton Airport (BCT), Boca Raton, Florida, about 1827.The owner of the airplane stated he had been receiving flight instruction from the pilot, and in return he offered to let the pilot borrow the airplane. The pilot stated that, at the conclusion of the flight, he approached the destination airport and calculated that the landing distance required was "between 2,010 and 2,100 feet." After an uneventful flare, the airplane touched down on runway 22 "shortly after" the runway numbers. After touchdown, the pilot immediately deployed the speed brakes, brakes, and thrust reversers. The pilot said the airplane had slowed to 60 knots at the intersection of runway 14-32, about 3,000 ft from the threshold of runway 22, so he put the thrust reversers in idle reverse. He had considered exiting at taxiway A, which was about 400 feet past the intersection of the two runways but felt it would have required maximum braking. The pilot said he then amended his plan and decided to exit the runway onto taxiway D at the departure end of runway 22, about 2,000 feet beyond the runway intersection. He stated during this time, between taxiway A and D, he held his feet off the brakes, estimating the airplane speed was 20-23 knots. He retracted the flaps, speed brakes, and the thrust reversers. He reported that, as the airplane approached taxiway D, he applied brakes and commented to the passenger, "we have no brakes." He pumped the brakes, then redeployed the speed brakes and thrust reversers and applied the emergency brake. Air traffic controllers in the SRQ tower stated that the airplane touched down in "the vicinity of the aiming point," and that after touchdown they "noticed that they might be a bit fast." The accident sequence was captured by surveillance cameras and a review of the video showed the airplane touched down approximately abeam the B1 taxiway, 1,700 feet beyond the approach end of the runway, and that the thrust reversers were not deployed during the recorded portion of the landing roll. Runway 04/22 at SQR was 5,009 ft long and 150 ft wide; runway 14/32 at SQR was 9,500 ft long and 150 ft wide. Taxiway B was 1,700 feet from the threshold of runway 22, taxiway A was 3,400 feet from the threshold of runway 22. Taxiway A was about 1,600 ft from taxiway D and the departure end of the runway. Postaccident examination of the airplane by a Federal Aviation Administration inspector and an airframe and powerplant mechanic revealed a puncture in the pressure vessel aft of the nose landing gear and damage to the bulkhead belly stringers. Functional testing of the brakes showed that they were operational and did not reveal evidence any pre- or post-impact mechanical anomalies. According to photographs and diagrams prepared by airport management, skid marks that aligned directly with the airplane's tire tracks in the grass began 1,130 feet prior to the departure end of the runway, just past taxiway A. The pilot held an airline transport pilot certificate with type ratings for Cessna CE-500 and CE-525 airplanes. His most recent FAA second-class medical certificate was issued on March 18, 2015. Review of flight experience documents provided by the pilot's attorney revealed that the pilot reported 4075 hours of flight experience, of which 1,713 were in turbine-powered airplanes. The 7-seat, low-wing airplane was manufactured in 1978, was powered by two Pratt and Whitney JT15D-4 turbofan engines, and was certified as a two-pilot airplane. Its most recent Phase 1-5 inspections were completed May 29, 2015 at 9,212.9 total aircraft hours. The airplane accrued 52.6 hours since that date. At 1853, the weather reported at SRQ included few clouds at 2,220 and 3,100 feet, calm wind, and 10 miles visibility. The temperature was 27°C, the dewpoint was 25°C, and the altimeter setting was 29.89 inches of mercury. The airline transport pilot was landing at the destination airport at the conclusion of a personal flight. Although the pilot reported that the airplane touched down near the threshold of the runway and that he used speed brakes, brakes, and thrust reversers to slow the airplane, review of a surveillance video revealed that the airplane touched down about 1,700 ft past the runway threshold of the 5,000-ft-long runway and that the thrust reversers were not deployed during the recorded portion of the landing roll. The airplane's tires left over 1,300 ft of skid marks before it overran the departure end of the runway, which resulted in substantial damage. While the pilot stated that the brakes had malfunctioned during the landing, examination and postaccident testing of the brakes revealed no evidence of any mechanical anomalies. Based on the available evidence, it is likely that the pilot landed the airplane well beyond the runway threshold and did not apply adequate braking effort until insufficient runway remained to stop the airplane on the paved surface. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2015_ERA15LA380.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 (runway excursion). 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 2013 · Conference Paper
Cockpit Resource Management (CRM) training in the 1550th combat crew training wing
The training program the 1550th Combat Crew Training Wing at Kirtland Air Force Base, New Mexico, implemented in September 1985 is discussed.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
Browse the full corpus — academia portal ↗