# NTSB investigations: Cessna 525

A list on [Cessna 525](https://openairdocs.org/model/cessna-525.md).

Matched to the registry by N-number and event date, newest first.

- [NTSB GAA22WA017](https://openairdocs.org/ntsb/GAA22WA017.md): Cessna 525 · Bristol, United Kingdom · Incident · No injuries · Class 5 · Foreign · Oct 20, 2021 · N498YY · No damage
- [NTSB GAA19CA467](https://openairdocs.org/ntsb/GAA19CA467.md): Cessna 525 · Orlando, FL · Accident · No injuries · Data collection · Final report · Jul 12, 2019 · N262BK · Substantial damage
  > The airplane’s impact with a bird during approach.
- [NTSB CEN18FA326](https://openairdocs.org/ntsb/CEN18FA326.md): Cessna 525 · Payson City, UT · Accident · 1 fatal · Field investigation · Final report · Aug 13, 2018 · N526CP · Substantial damage
  > The pilot's intentional flight into his residence.
- [NTSB ERA18FA127](https://openairdocs.org/ntsb/ERA18FA127.md): Cessna 525 · Crozet, VA · Accident · 1 fatal · Field investigation · Final report · Apr 16, 2018 · N525P · Destroyed
  > The pilot's loss of control while operating in night instrument meteorological conditions as a result of spatial disorientation. Contributing to the accident was the pilot's decision to operate an airplane after consuming alcohol and his resulting…
- [NTSB WPR16FA054](https://openairdocs.org/ntsb/WPR16FA054.md): Cessna 525 · Cedar Fort, UT · Accident · 2 fatal · Field investigation · Final report · Jan 18, 2016 · N711BX · Destroyed
  > The pilot's loss of control due to spatial disorientation while operating in instrument meteorological conditions, which resulted in an exceedance of the airplane's design stress limitations, and a subsequent in-flight breakup. Contributing to the accident…
- [NTSB CEN15RA446](https://openairdocs.org/ntsb/CEN15RA446.md): Cessna 525 · Geneva, Switzerland · Incident · No injuries · Foreign investigation · Jul 24, 2015 · N990FV · 2 aircraft · No damage
- [NTSB CEN14LA129](https://openairdocs.org/ntsb/CEN14LA129.md): Cessna 525 · Elk City, OK · Accident · No injuries · Limited investigation · Final report · Feb 4, 2014 · N61YP · Substantial damage
  > The pilot’s descent below the published minimum descent altitude for the instrument approach procedure, which resulted in impact with a utility pole.
- [NTSB CEN10WA308](https://openairdocs.org/ntsb/CEN10WA308.md): Cessna 525 · Leeds, United Kingdom · Accident · No injuries · Class 5 · Foreign · Jun 7, 2010 · N646VP · Substantial damage
  > On June 7, 2010, at 1650 coordinated universal time, a Cessna 525, N646VP, overran runway 14 during an aborted takeoff at the Leeds Bradford International Airport, Leeds, England. There were no injuries. The investigation is under the jurisdiction of the…
- [NTSB MIA08MA051](https://openairdocs.org/ntsb/MIA08MA051.md): Cessna 525 · West Gardiner, ME · Accident · 2 fatal · Major investigation · Final report · Feb 1, 2008 · N102PT · Destroyed
  > The pilot's spatial disorientation and subsequent failure to maintain airplane control.
- [NTSB LAX07MA069](https://openairdocs.org/ntsb/LAX07MA069.md): Cessna 525 · Van Nuys, CA · Accident · 2 fatal · Major investigation · Final report · Jan 12, 2007 · N77215 · Destroyed
  > The pilot's failure to maintain an adequate airspeed during the initial climb resulting in an inadvertent stall/spin. Contributing to the accident were the second pilots inadequate preflight, failure to properly secure the front baggage door, and the front…
- [NTSB ATL06CA080](https://openairdocs.org/ntsb/ATL06CA080.md): Cessna 525 · Murfreesboro, TN · Accident · No injuries · Data collection · Final report · May 16, 2006 · N545TG · Substantial damage
  > The pilot's failure to maintain directional control while landing on a wet runway.
- [NTSB IAD05LA099](https://openairdocs.org/ntsb/IAD05LA099.md): Cessna 525 · Old Bridge, NJ · Accident · Minor injuries · Limited investigation · Final report · Jul 17, 2005 · N13FH · Substantial damage
  > The pilot's improper preflight planning, his failure to consult performance data, and his failure to obtain the proper touchdown point, which resulted in a runway overrun. Contributing factors to the accident were the excessive airspeed, overweight condition,…
- [NTSB SEA03FA147](https://openairdocs.org/ntsb/SEA03FA147.md): Cessna Citation 525 · Coupeville, WA · Accident · No injuries · Field investigation · Final report · Jul 22, 2003 · N996JR · Substantial damage
  > The loss of airplane pitch control (trim runway and mistrim condition) resulting from a failure in the airplane's electric pitch trim system. Factors that contributed to the accident were the manufacturer's inadequate design of the pitch trim circuitry that…
- [NTSB MIA01WA098](https://openairdocs.org/ntsb/MIA01WA098.md): Cessna 525 · Hamburg, Germany · Accident · No injuries · Foreign investigation · Mar 8, 2001 · N909M · Substantial damage
- [NTSB DCA01WA018](https://openairdocs.org/ntsb/DCA01WA018.md): Cessna CitationJET (525) · Salcea, Romania · Accident · No injuries · Foreign investigation · Jan 31, 2001 · N1127K · Substantial damage
- [NTSB FTW00FA103](https://openairdocs.org/ntsb/FTW00FA103.md): Cessna 525 · Buda, TX · Accident · 1 fatal · Field investigation · Final report · Mar 26, 2000 · N130MR · Destroyed
  > the pilot's inadequate in-flight decision to continue a visual approach in instrument meteorological conditions which resulted in his failure to maintain terrain clearance. Contributing factors were the fog, drizzle, and low ceilings.
- [NTSB CHI00FA040](https://openairdocs.org/ntsb/CHI00FA040.md): Cessna 525 · Branson, MO · Accident · 6 fatal · Field investigation · Final report · Dec 9, 1999 · N525KL · Destroyed
  > the pilot descended below the minimum altitude for the segment of the GPS approach. Factors relating to the accident were low ceilings, rain, and pilot fatigue.
- [NTSB ATL98FA060](https://openairdocs.org/ntsb/ATL98FA060.md): Cessna 525 · Marietta, GA · Accident · 5 fatal · Field investigation · Final report · Apr 4, 1998 · N111LR · 2 aircraft · Destroyed
  > The failure of both pilots to see and avoid conflicting traffic, and the failure of the 172 pilot to operate the transponder as required by current regulations. Factors were the controller's failure to observe the traffic conflict, the lack of radar conflict…

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('2076601', '2076653')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/model/cessna-525/ntsb

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
