If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user

 Actions

Paris/Charles de Gaulle Airport

From SKYbrary Wiki

LFPG
Airport
ICAO: LFPG – IATA: CDG
Summary
Name Paris/Charles de Gaulle Airport
Region Europe
Territory France FR.gif
Location Roissy-en-France, Ile-de-France
Serving Paris
Elevation 119.482 m
392 ft
392 ft119.482 m
Type large airport
Coordinates 49° 0' 31.49" N, 2° 32' 36.83" E
Runways
Designator Length Width Surface ROPS
08L/26R 4215 m13,828.74 ft
45 m147.638 ft
ASP yes/yes
08R/26L 2700 m8,858.268 ft
60 m196.85 ft
CON yes/yes
09L/27R 2700 m8,858.268 ft
60 m196.85 ft
ASP yes/yes
09R/27L 4200 m13,779.528 ft
45 m147.638 ft
ASP yes/yes


METAR
Observation LFPG 150330Z 22019G30KT 9999 FEW018 BKN019 11/08 Q0997 TEMPO 20020G35KT 4000 SHRA SCT015TCU BKN020
Station Paris-Aeroport Charles De Gaulle
Date/Time 15 December 2019 03:30:00
Wind direction 220°
Wind speed 19 kts
Lowest cloud amount few clouds
Temperature 11°C
Dew point 8°C
Humidity 81%
QNH 997 hPa
Weather condition n/a

LOS
Tag(s) Parallel Runway Operation

Paris/Charles De Gaulle Airport

ICAO: LFPG IATA: CDG

Description

International airport serving Paris.

Climatology

Temperate Marine climate/Oceanic climate (Köppen climate classification Cfb). Moderately cool summer and comparatively warm winter. Prevailing south-westerly winds from the Atlantic Ocean.

Maps

Terrain

Loading map...

Airport Layout

Loading map...


Accidents & Serious Incidents at or in vicinity of LFPG

  • A306, Paris CDG France, 1997 (On 30 July 1997, an Airbus A300-600 being operated by Emirates Airline was departing on a scheduled passenger flight from Paris Charles de Gaulle in daylight when, as the aircraft was accelerating at 40 kts during the take off roll, it pitched up and its tail touched the ground violently. The crew abandoned the takeoff and returned to the parking area. The tail of the aircraft was damaged due to the impact with the runway when the plane pitched up.)
  • A319 / A320, Paris CDG France, 2014 (On 25 November 2014, the crew of an Airbus A320 taking off from Paris CDG and in the vicinity of V1 saw an A319 crossing the runway ahead of them and determined that the safest conflict resolution was to continue the takeoff. The A320 subsequently overflew the A319 as it passed an estimated 100 feet agl. The Investigation concluded that use of inappropriate phraseology by the TWR controller when issuing an instruction to the A319 crew had led to a breach of the intended clearance limit. It was also noted that an automated conflict alert had activated too late to intervene.)
  • A343, vicinity Paris CDG France, 2012 (On 13 March 2012, an A340-300 crew cleared for a Cat 3 ILS approach at Paris CDG with LVP in force failed to descend at a rate which would allow the aircraft to capture the ILS GS and at 2nm from the runway, when still 2500 feet above runway height, the ILS GS mode engaged on a false upper lobe of about 10° and as a result of the consequent rapid pitch up and speed reduction, aircraft control was almost lost. After a period of further confusion, a go around was initiated and the subsequent approach was uneventful.)
  • B733, Paris CDG France, 2011 (On 23 July 2011, a Boeing 737-300 being operated by Jet2.com on a passenger flight from Leeds/Bradford to Paris CDG experienced violent vibration from the main landing gear at touch down in normal day visibility on runway 27R at a normal speed off a stabilised approach. This vibration was accompanied by lateral acceleration that made directional control difficult but the aircraft was kept on the runway and at a speed of 75 knots, the vibrations abruptly stopped. Once clear of the runway, the aircraft was stopped and the engines shutdown prior to a tow to the gate. None of the 133 occupants were injured.)
  • B738, Paris CDG France, 2008 (On 16 August 2008, an AMC Airlines’ Boeing 737-800 inadvertently began a night take off from an intersection on runway 27L at Paris CDG which left insufficient take off distance available before the end of the temporarily restricted runway length. It collided with and damaged obstructions related to construction works in progress on the closed section of the runway but sustained only minor damage and completed the intended flight to Luxor. The context for the flight crew error was identified as inadequate support from the Operator and inadequate airport risk assessment for operations with a reduced runway length.)

... further results