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

AIRBUS A-330-300

From SKYbrary Wiki
Name A-330-300
Manufacturer AIRBUS
Body Wide
Wing Fixed Wing
Position Low wing
Tail Regular tail, mid set
WTC Heavy
Type code L2J
Aerodrome Reference Code 4E
Engine Jet
Engine count Multi
Position Underwing mounted
Landing gear Tricycle retractable
Mass group 4

Manufacturered as:

AIRBUS A-330-300

AIRBUS A-330-300

AIRBUS A-330-300 AIRBUS A-330-300 3D


Large capacity long range airliner. In service since 1993. Largest member of Airbus twinjet family (2-engine version of A340). Total of 253 aircraft ordered and 193 in operation (August 2006). The A333 is member of the A330 family of aircraft.

Technical Data

Wing span 60.3 m197.835 ft
Length 63.69 m208.957 ft
Height 16.83 m55.217 ft
Powerplant 2 x GE CF6-80E1 (306kN) or
2 x R-R Trent 772 (300kN) or
2 x PW 4000 (308kN) turbofans.
Engine model General Electric CF6, Pratt & Whitney PW4000, Rolls-Royce Trent 700

Performance Data

Take-Off Initial Climb
(to 5000 ft)
Initial Climb
(to FL150)
Initial Climb
(to FL240)
MACH Climb Cruise Initial Descent
(to FL240)
(to FL100)
Descent (FL100
& below)
V2 (IAS) 145 kts IAS 175 kts IAS 290 kts IAS 290 kts MACH 0.8 TAS 475 kts MACH 0.81 IAS 290 kts IAS kts Vapp (IAS) 130 kts
Distance 2300 m ROC 2000 ft/min ROC 2000 ft/min ROC 1300 ft/min ROC 1000 ft/min MACH 0.81 ROD 1000 ft/min ROD 3000 ft/min MCS 200 kts Distance 1700 m
MTOW 230000230,000 kg
230 tonnes
Ceiling FL410 ROD ft/min APC C
WTC H Range 61006,100 nm
11,297,200 m
11,297.2 km
37,064,304.489 ft

Accidents & Serious Incidents involving A333

  • A332 / A333, en-route, North West Australia, 2012 (On 31 March 2012, after the implementation of contingency ATC procedures for a period of 5 hours due to controller shortage, two Garuda A330 aircraft which had been transiting an associated Temporary Restricted Area (TRA) prior to re-entering controlled airspace were separately involved in losses of separation assurance, one when unexpectedly entering adjacent airspace from the TRA, the other when the TRA ceased and controlled airspace was restored. The Investigation did not find that any actual loss of separation had occurred but identified four Safety Issues in relation to the inadequate handling of the TRA activation by ANSP Airservices Australia.)
  • A333, Hong Kong China, 2010 (On 13 April 2010, a Cathay Pacific Airbus A330-300 en route from Surabaya to Hong Kong experienced difficulty in controlling engine thrust. As these problems worsened, one engine became unusable and a PAN and then a MAYDAY were declared prior to a successful landing at destination with excessive speed after control of thrust from the remaining engine became impossible. Emergency evacuation followed after reports of a landing gear fire. Salt water contamination of the hydrant fuel system at Surabaya after alterations during airport construction work was found to have led to the appearance of a polymer contaminant in uplifted fuel.)
  • A333, Kathmandu Nepal, 2015 (On 4 March 2015, the crew of a Turkish Airlines A333 continued an automatic non precision RNAV approach below the prescribed minimum descent altitude without having obtained any element of visual reference and when this was acquired a few seconds before the attempted landing, the aircraft was not aligned with the runway centreline and during a 2.7g low-pitch landing, the left main gear touched down on the grass. The aircraft then left the runway completely before stopping with a collapsed nose gear and sufficient damage to be assessed a hull loss. None of 235 occupants sustained serious injury.)
  • A333, Manila Philippines, 2013 (On 7 October 2013 a fire was discovered in the rear hold of an Airbus A330 shortly after it had arrived at its parking stand after an international passenger flight. The fire was eventually extinguished but only after substantial fire damage had been caused to the hold. The subsequent Investigation found that the actions of the flight crew, ground crew and airport fire service following the discovery of the fire had all been unsatisfactory. It also established that the source of the fire had been inadequately packed dangerous goods in passengers checked baggage on the just-completed flight.)
  • A333, en-route, Kota Kinabalu Malaysia, 2009 (On 22 June 2009, an Airbus A330-300 being operated by Qantas on a scheduled passenger flight from Hong Kong to Perth encountered an area of severe convective turbulence in night IMC in the cruise at FL380 and 10 of the 209 occupants sustained minor injuries and the aircraft suffered minor internal damage. The injuries were confined to passengers and crew who were not seated at the time of the incident. After consultations with ground medical experts, the aircraft commander determined that the best course of action was to complete the flight as planned, and this was uneventful.)
  • A333, en-route, West of Learmonth Australia, 2008 (On 7 October 2008, an Airbus A330-300 aircraft experienced multiple system failure indications followed by uncommanded pitch-down events which resulted in serious injuries to passengers and cabin crew.)
  • A333, en-route, near Bournemouth UK, 2012 (On 16 April 2012, a Virgin Atlantic A330-300 made an air turnback to London Gatwick after repetitive hold smoke detector warnings began to occur during the climb. Continuing uncertainty about whether the warnings, which continued after landing, were false led to the decision to order an emergency evacuation on the runway. Subsequent investigation found that the smoke warnings had all been false and had mainly come from one faulty detector. It also found that aspects of the way the evacuation had taken place had indicated where there were opportunities to try and improve passenger behaviour.)
  • A333, en-route, south of Moscow Russia, 2010 (On 22 December 2010, a Finnair Airbus A330-300 inbound to Helsinki and cruising in very cold air at an altitude of 11,600 metres lost cabin pressurisation in cruise flight and completed an emergency descent before continuing the originally intended flight at a lower level. The subsequent Investigation was carried out together with that into a similar occurrence to another Finnair A330 which had occurred 11 days earlier. It was found that in both incidents, both engine bleed air systems had failed to function normally because of a design fault which had allowed water within their pressure transducers to freeze.)
  • A333, vicinity Orlando FL USA, 2013 (On 19 January 2013, a Rolls Royce Trent 700-powered Virgin Atlantic Airbus A330-300 hit some medium sized birds shortly after take off from Orlando, sustaining airframe impact damage and ingesting one bird into each engine. Damage was subsequently found to both engines although only one indicated sufficient malfunction - a complete loss of oil pressure - for an in-flight shutdown to be required. After declaration of a MAYDAY, the return to land overweight was completed uneventfully. The investigation identified an issue with the response of the oil pressure detection and display system to high engine vibration events and recommended modification.)
  • A333, vicinity Wom Guam Airport, Guam, 2002 (On 16 December 2002, approximately 1735 UTC, an Airbus A330-330, operating as Philippine Airlines flight 110, struck power lines while executing a localizer-only Instrument Landing System (ILS) approach to runway 6L at A.B. Pat Won Guam International Airport, Agana, Guam. Instrument meteorological conditions prevailed during the approach. Following a ground proximity warning system (GPWS) alert, the crew executed a missed approach and landed successfully after a second approach to the airport.)

Further Reading

  • Airbus reference document which provide to airlines, MROs, airport planners and operators the general dimensions of the aircraft, as well as the necessary information for ramp, servicing operations or maintenance preparation: Airbus A330: Airplane characteristics for aiport planning AC, 01 April 2013