# Taxiway lighting

- Type: NTSB finding subsection
- Path: [Environmental issues](https://openairdocs.org/ntsb-findings/03) › [Operating environment](https://openairdocs.org/ntsb-findings/0301) › [Airport facilities/design](https://openairdocs.org/ntsb-findings/030170) › Taxiway lighting
- NTSB code: 03017020
- Cases: 5
- In the probable cause: 2
- Fatal cases: 0
- All cases: https://openairdocs.org/ntsb-findings/03017020/cases.md
- Cases with it in the probable cause: https://openairdocs.org/ntsb-findings/03017020/cases.md?cause=1
- Page: https://openairdocs.org/ntsb-findings/03017020

## Cases per year (in the probable cause / all)

- 2009: 1 / 1
- 2013: 0 / 1
- 2015: 1 / 3

## Defining events in these cases

- [Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330): 1 cases
- [Wrong surface or wrong airport](https://openairdocs.org/ntsb-events/284): 1 cases
- [Loss of control on ground](https://openairdocs.org/ntsb-events/230): 1 cases
- [Ground collision](https://openairdocs.org/ntsb-events/200): 1 cases
- [Landing gear collapse](https://openairdocs.org/ntsb-events/094): 1 cases

## Aircraft models (registry)

- [Raytheon A36](https://openairdocs.org/model/raytheon-a36): 1 cases
- [Piper PA-28R-200](https://openairdocs.org/model/piper-pa-28r-200): 1 cases
- [Cessna 195](https://openairdocs.org/model/cessna-195): 1 cases
- [Boeing 767-332](https://openairdocs.org/model/boeing-767-332): 1 cases
- [Boeing 737-3H4](https://openairdocs.org/model/boeing-737-3h4): 1 cases

## Other findings in the same cases

- [Decision making/judgment](https://openairdocs.org/ntsb-findings/02041520) (Personnel issues): 2 cases
- [Alertness/Fatigue, general](https://openairdocs.org/ntsb-findings/02013500) (Personnel issues): 2 cases
- [Surface speed/braking](https://openairdocs.org/ntsb-findings/01062045) (Aircraft): 2 cases
- [Exterior lighting](https://openairdocs.org/ntsb-findings/01023340) (Aircraft): 2 cases
- [Equipment design](https://openairdocs.org/ntsb-findings/04011010) (Organizational issues): 1 cases
- [Taxiway markings/signage](https://openairdocs.org/ntsb-findings/03017040) (Environmental issues): 1 cases
- [Runway lighting](https://openairdocs.org/ntsb-findings/03017015) (Environmental issues): 1 cases
- [Surface/taxi](https://openairdocs.org/ntsb-findings/03015010) (Environmental issues): 1 cases
- [Localizer](https://openairdocs.org/ntsb-findings/03012020) (Environmental issues): 1 cases
- [Approach lighting](https://openairdocs.org/ntsb-findings/03012015) (Environmental issues): 1 cases

## Newest cases

- [NTSB DCA16LA032](https://openairdocs.org/ntsb/DCA16LA032), Dec 15, 2015: Boeing 737 3H4 (N649SW), Nashville, TN, substantial damage. Probable cause: the flight crew's early turn towards the assigned gate because taxiway lighting had been inadvertently turned off by the controller-in-charge which resulted in the airplane leaving the paved surface.…
- [NTSB GAA16CA005](https://openairdocs.org/ntsb/GAA16CA005), Oct 6, 2015: Raytheon A36 (N53WW), Monterey, CA, substantial damage. Probable cause: The pilot's failure to see and avoid runway signage during taxi after landing, resulting in a collision and substantial damage to the left wing of the airplane.
- [NTSB GAA15CA263](https://openairdocs.org/ntsb/GAA15CA263), Sep 7, 2015: Piper PA 28R-200 (N1125X), Doylestown, PA, substantial damage. Probable cause: The pilot's failure to land with sufficient runway remaining to safely stop the airplane. Contributing to the accident was the pilot's fatigue during the flight.
- [NTSB CEN13LA170](https://openairdocs.org/ntsb/CEN13LA170), Feb 17, 2013: Cessna 195 (N4426C), Austin, TX, substantial damage. Probable cause: The pilot's use of an excessive taxi speed, which resulted in the airplane overrunning the end of the unlit taxiway after the failure of the right wing landing light.
- [NTSB OPS10IA001](https://openairdocs.org/ntsb/OPS10IA001), Oct 19, 2009: Boeing 767 (N185DN), Atlanta Hartsfield Intl. Apt. (KATL), GA, incident, no damage. Probable cause: 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…

NTSB has coded findings and defining events since 2008; earlier cases used its older occurrence and cause codes and aren't counted.

Findings: https://openairdocs.org/ntsb-findings.md. Defining events: https://openairdocs.org/ntsb-events.md. Phases of flight: https://openairdocs.org/ntsb-phases.md. Every investigation, filtered by finding, event, phase, state, year or model: https://openairdocs.org/ntsb.md (for example ?state=MI&fatal=1).

NTSB's definitions: Accident and incident, 49 CFR 830.2 (https://www.ecfr.gov/current/title-49/subtitle-B/chapter-VIII/part-830/subpart-A/section-830.2), CICTT occurrence categories (PDF) (https://www.ntsb.gov/safety/data/Documents/datafiles/OccurrenceCategoryDefinitions.pdf), CICTT phases of flight (PDF) (https://www.ntsb.gov/safety/data/Documents/datafiles/PhaseofFlightDefinitions.pdf), and NTSB coding manual, before 2008 (PDF) (https://www.ntsb.gov/GILS/Documents/codman.pdf). NTSB publishes no definitions for its findings, only their names.

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