# NTSB investigations: Approach lighting

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB GAA19CA525](https://openairdocs.org/ntsb/GAA19CA525.md): Cessna 182 · Charleston, WV · Accident · Minor injuries · Data collection · Final report · Sep 5, 2019 · N2408Q · Substantial damage
  > The pilot's improper approach path at night and his misjudgment of the landing point, which resulted in landing short of the runway and impact with the runway's engineered materials arrestor system.
- [NTSB CEN16LA016](https://openairdocs.org/ntsb/CEN16LA016.md): Cirrus Design SR22 · Lancaster, TX · Accident · Serious injuries · Limited investigation · Final report · Oct 17, 2015 · N849CD · Destroyed
  > The pilot’s failure to maintain a proper glidepath during a night visual approach, which resulted in impact with a power line. Contributing to the accident was an inoperative precision approach path indicator.
- [NTSB OPS10IA001](https://openairdocs.org/ntsb/OPS10IA001.md): Boeing 767 · Atlanta Hartsfield Intl. Apt. (KATL), GA · Incident · No injuries · Incident investigation · Final report · Oct 19, 2009 · N185DN · No damage
  > The flight crew’s failure to identify the correct landing surface due to fatigue. Contributing to the cause of the incident were (1) the flight crew’s decision to accept a late runway change, (2) the unavailability of the approach light system and the…
- [NTSB SEA08LA082](https://openairdocs.org/ntsb/SEA08LA082.md): Raytheon 1900D · Kayenta, AZ · Accident · Serious injuries · Limited investigation · Final report · Feb 22, 2008 · N305PC · Substantial damage
  > The flight crew's failure to execute a missed approach, which resulted in a runway excursion after landing. Contributing to the accident were the inoperative lights, weather conditions below published approach minimums, and the slush contaminated runway.

## 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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '03012015'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb-findings/03012015/cases

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