FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Turkish Airlines Flight 634

8 Jan 2003 · Diyarbakır Airport, Diyarbakır, Turkey

Avro RJ100 · Controlled flight into terrain in poor visibility due to pilot error

From İstanbul Atatürk Airport (ISL) to Diyarbakır Airport, Diyarbakır, Turkey

Report a problem

Event

NTSB case
DCA03WA023
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
Accident
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
Event fatalities
75 · all aircraft and ground
Ground fatalities
Unknown
Occupants
80
Survivors
5
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
5
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

Avro RJ100

Flight
TK634
Aircraft type
Avro RJ100
Category
Airplane
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
TC-THG
Onboard fatalities
75
Route
From İstanbul Atatürk Airport (ISL)To Diyarbakır Airport, Diyarbakır, Turkey
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
Unknown
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
Not recorded
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
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Estimated position: Diyarbakır Airport, the airport the Wikipedia article names as the site. Where on or near it is not known.

From the Wikipedia article

Turkish Airlines Flight 634 was a scheduled domestic passenger flight from Istanbul Atatürk Airport to Diyarbakır Airport in southeastern Turkey. On 8 January 2003 at 20:19 EET (18:19 UTC), the aircraft operating the flight, a British Aerospace Avro RJ100, struck the ground on final approach approximately 900 m short of the runway threshold during inclement weather conditions. In the following collision with a slope, a post-crash fire broke out, killing 75 of the 80 occupants, including the entire crew. This is the deadliest aviation accident to involve the BAe 146.

Accident

Flight 634 departed Istanbul Atatürk Airport at 18:43 EET (16:43 UTC) for the nearly two-hour flight to Diyarbakır in southeastern Turkey. Approximately one hour into the flight and 40 nmi off the destination airport, the crew contacted Diyarbakir Airport's approach control, which cleared the flight to approach the airport from the south for runway 34 using VHF omnidirectional range – a type of short-range radio navigation system which enables aircraft with a receiving unit to determine their position and stay on course – and instructed the crew to descend to 9000 ft. The weather report relayed to crew by the controller stated no winds and visibility of 3500 m.

When the flight was 8 nmi from runway 34 and at an altitude of 5000 ft, air traffic control instructed the crew to continue the approach and report as soon as they had established visual contact with the runway. The crew acknowledged the call and prepared the aircraft for landing, deploying the landing gear and extending the flaps. Continuing to descend, the aircraft reached its minimum descent altitude (MDA) of 2800 ft – the lowest altitude to which descent is authorized on final approach or during circle-to-land maneuvering in execution of a standard instrument approach procedure where no electronic glideslope is provided (the airport was not equipped with an instrument landing system) – but both pilots said that they still had no visual reference to the runway or its approach lighting system because of the thick fog. One pilot discerned some lights in the distance but was not sure what exactly they belonged to.

Nonetheless, violating standard procedures, the captain decided to continue the approach to as close as 1 mi to the runway and descended further to 500 ft and beyond, well below the MDA. At 1 mi off the threshold of the runway and at an altitude of 200 ft (which in this case constituted the decision height), the ground proximity warning system (GPWS) started to trigger aural alarms. Eight seconds later, the crew decided to abort the landing and initiated a go-around, but before being able to execute the command, the airplane struck the ground with the undersurface of the fuselage and the landing gear at 20:19 EET (18:19 UTC), 900 m off the threshold of runway 34 and 30 m off the approach lights at a speed of around 131 kn.

The aircraft slid on the ground for about 200 m while starting to disintegrate. Eventually, it hit a slope, broke up into three major pieces, exploded and caught fire; most of the bodies and parts of the wreckage were burnt. The debris was spread out in an area of about 800 m2.

The impact instantly killed both pilots, the three flight attendants and 69 of the 75 passengers. Six passengers survived, one of whom however later succumbed to his injuries in hospital.

Investigation and cause

Investigation

The investigation into the accident was carried out by Turkey's Directorate General of Civil Aviation (DGCA). Both flight recorders – the cockpit voice recorder (CVR) and the flight data recorder (FDR) – were found intact and were sent to Turkish Airlines' laboratories for analysis.

According to records, Captain Yunak and First Officer Ulusu were found to have been properly trained, qualified and experienced. They had sufficient rest before reporting for duty on the day of the accident. Drug and alcohol tests returned negative results.

Investigators also turned their attention to the aircraft, but were not able to detect any abnormalities. All maintenance checks were completed properly. Close examination of the engines revealed that they were operating normally at the time of the accident. The aircraft was properly configured for landing – the flaps and the landing gear were extended properly and the altimeter was set correctly – and the ground proximity warning system (GPWS) also produced alarms which could be easily heard on the CVR recordings.

Search and rescue teams who immediately rushed to the site to respond to the crash reported thick fog at the crash site and complained about the lack of visibility which according to their account was as low as 1 m at times. This clearly contradicts the weather report the air traffic controller at Diyarbakır Airport had relayed to the crew minutes before the crash. According to them, the fire could not even be seen until arriving on the scene.

Analysis of the FDR and the CVR revealed that at the moment the aircraft struck the ground it was at a heading of 339° (north-northwest, in line with the runway centerline) and 900 m short of the threshold of runway 34 at a positive pitch angle of five degrees (which corresponds to a slight nose-up position). The autopilot was found to have been activated up until a short time before the accident.

Final report

The investigation was completed around two years later in April 2005 and concluded that:

The Turkish Airline Pilots Association stated that an instrument landing system might have prevented the accident.

Text from the Wikipedia article “Turkish Airlines Flight 634” (revision 1355794150, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

Sources

Wikipedia article: Turkish Airlines Flight 634
Article
Turkish Airlines Flight 634
Revision
1355794150 · 2026-05-23 · retrieved 2026-09-18
Wikidata
Q1037884
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA03WA023
Event ID
20030110X00048
Case number
DCA03WA023
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
Wikipedia article "Turkish Airlines Flight 634" (page 20869433, revision 1355794150); merged with NTSB case DCA03WA023 (events / aircraft)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia: airport the Wikipedia infobox site links (Wikidata code, OurAirports)
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA03WA023
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Turkish Airlines Flight 634" and NTSB case DCA03WA023, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • No bulk values were replaced by the NTSB case API.