Jet2.com Flight LS177
Boeing 737 804 · Incident: fire/smoke (non-impact) during takeoff
Event
- NTSB case
- DCA13WA005
- 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
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Unknown · led by another country; figures from NTSB notifications
- 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
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Boeing 737 804
- Aircraft type
- Boeing 737
- Category
- Airplane · from aircraft type
- 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
- G-GDFJ
- Operator
- Jet2.com
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- 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 129: Foreign
- 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
- Takeoff · rejected takeoff
- 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
- Fire/smoke (non-impact)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Estimated position: the centre of Glasgow, the place the record names. Not the accident site.
NTSB narrative
On October 19, 2012, at 0655 UTC time, a Boeing 737-800, registration G-GDFJ, operated by Jet2.com as a scheduled passenger flight LS177 between Glasgow, Scotland and Alicante, Spain, rejected the takeoff due to smoke in the cabin. The aircraft stopped on the runway, and the passengers evacuated via the escape slides. Airplane damage is being assessed. There were 189 passengers and crew on board the aircraft, and an unknown number were injured during the evacuation.
The investigation is being conducted by the Air Accident Investigation Branch, Department for Transport of the United Kingdom. The NTSB has appointed an Accredited Representative to assist the investigation under the provisions of ICAO Annex 13 as the State of Manufacture and Design, of the airplane, and State of Manufacture of the engines.
All requests for information should be directed to:
AAIB Farnborough House Berkshire Copse Road Aldershot, Hampshire GU11 2HH, United Kingdom +44(0) 1252 510300
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record DCA13WA005
- Event ID
- 20121019X60625
- Case number
- DCA13WA005
- 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.
- No bulk values were replaced by the NTSB case API.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ce8bfb50d7085be4234c7112ad3b338b9ffb35e73bd850e42652954440d7a84f; retrieved 2026-09-15T20:13:17.904Z.