Skip to main content

AAIB Bulletin: 6/2007 G-OOSI EW/A2006/12/02

Cessna 404 Titan · Other Documents

Free account — keep the POHs & checklists you reference in one place.

Overview

This document is an incident report concerning the Cessna 404 Titan aircraft, registration G-OOSI. It details an incident that occurred on December 6, 2006, during a private flight from San Pedro Airport, Cape Verde Islands, to Dakar Airport, Senegal. The report outlines the circumstances leading to the incident, including the pilot's failure to use continuous oxygen above 10,000 feet, which likely resulted in hypoxia. The document includes a thorough investigation of the flight history, the actions taken during the incident, and the subsequent assessment of the aircraft's condition. It also discusses the operator's response and planned changes to procedures to prevent similar occurrences in the future.

  • The Cessna 404 Titan is equipped with a factory-fitted oxygen system, typically located in the nose compartment.
  • The aircraft's altitude operating limitation is 10,000 feet without oxygen equipment.
  • The oxygen pressure indicator showed 1,200 psi before the flight, allowing over four hours of oxygen use for two people at FL220.
  • The pilot experienced hypoxia due to not using the oxygen mask continuously above 10,000 feet.
  • The company will implement more stringent hypoxia training and require pilots to inform safety personnel of any unserviceable equipment.

Document

Source

Originally published by assets.publishing.service.gov.uk. Sprinkle hosts a reference copy with an added summary, specifications and searchable full text.

Report a problem or request removal

Document details

Type
Other Documents
Year
2007
Pages
3
File size
250 KB
Publisher
assets.publishing.service.gov.uk
How rare is it?
15Cessna 404 Titan registered worldwide · 0 active

Common. Rarer than 5% of the aircraft models we track.

Documentation completeness
5/7

Most owners only have the POH. Here's the essential set for the Cessna 404 Titan.

More Cessna 404 Titanmanuals & documents

See all 24
Similar aircraft

If you fly the Cessna 404 Titan, you may also be researching these.

In this document

Incident Overview

The incident involved the Cessna 404 Titan, G-OOSI, where the pilot did not use continuous oxygen above 10,000 feet, leading to hypoxia and an uncontrolled descent. The pilot regained control at a lower altitude and landed safely.

Flight History

Prior to the incident, the aircraft was used for map survey operations without significant issues. The pilot planned to cruise at FL220, aware of the oxygen requirements for the altitude.

Oxygen System Details

The Cessna 404 is equipped with an oxygen system, typically located in the nose compartment. However, G-OOSI had modifications that placed the oxygen cylinder at the rear of the cabin, complicating its use during flight.

Pilot's Assessment

Post-incident, the pilot acknowledged the risks of hypoxia and recognized that he underestimated the need for continuous oxygen use during the flight.

Company Actions

The operating company concluded that the pilot's failure to use oxygen continuously was a major factor in the incident. They plan to implement stricter training and procedural changes to enhance safety.

Safety notes

  • All aircraft must fly below 10,000 feet unless equipped with a pressurized cabin or individual oxygen sources.
  • Oxygen is recommended at lower altitudes when flying at night.

Full document text

46 © Crown copyrght 2007 AAIB Bulletin: 6/2007 G-OOSI EW/A2006/12/02 INCIDENT Aircraft Type and Registration: Cessna 404 Ttan, G-OOSI No & Type of Engines: 2 Contnental GTSIO-520-M pston engnes Year of Manufacture: 98 Date & Time (UTC): 6 December 2006 at approxmately 90 hrs Location: En-route from San Pedro Arport, Cape Verde Islands, to Dakar Arport, Senegal Type of Flight: Prvate Persons on Board: Crew -  Passengers -  Injuries: Crew - None Passengers - None Nature of Damage: None Commander’s Licence: Commercal Plot’s Lcence wth Instrument Ratng Commander’s Age: 2 years Commander’s Flying Experience: 504 hours (of whch 5 were on type) Last 90 days - 85 hours Last 28 days - 5 hours Information Source: Arcraft Accdent Report Form submtted by the plot, a company report and enqures by the AAIB Introduction The ncdent occurred over nternatonal waters and, n agreement wth the Portuguese Authortes the AAIB, representng the State of Regstraton, took responsblty for the nvestgaton. Synopsis When flying above 10,000 ft, the commander did not use contnuous oxygen. He was probably sufferng from hypoxa when he attempted to adjust hs engne controls and ths resulted n vbraton and an uncontrolled descent. He recovered full control at a lower alttude and made a successful dverson. The operatng company s mplementng changes to ther operatng procedures to prevent a smlar occurrence. History of the flight The arcraft had been operatng n the area snce the end of November 2006 and was beng used for map survey operatons. Durng ths tme there were no reports of any significant aircraft unserviceability. The aircraft was usually operated on survey flights with two people on board: a plot (the commander) and a camera operator (the passenger). Prior to the incident flight, the commander had noted that hs ntended route from San Pedro Arport to Dakar Airport included a portion with a minimum notified alttude of FL95. He therefore planned a cruse alttude of FL20 but ntended to descend below FL00 when wthn the Dakar FIR. The arcraft oxygen pressure indicator was showing 1,200 psi before the flight which 47 © Crown copyrght 2007 AAIB Bulletin: 6/2007 G-OOSI EW/A2006/12/02 would allow just over four hours oxygen use for two people at FL220. The commander subsequently stated that the arcraft occupants would need oxygen for approxmately 45 mnutes. There were three plot-style oxygen masks for the two occupants. Each had a rubber restranng strap and a mcrophone. However, the commander was aware that the mcrophone on at least one of the masks was “crackly” and he ddn’t ntend to use t for rado transmssons. Addtonally, the mask provded to the passenger had a broken strap held together wth adhesve tape. The passenger stated that a week before this flight, he was advsed (by a dfferent commander) that he should only use oxygen “as and when he needed t” to avod any possblty of dranng the system. However, the operator’s representatve stated that no such nstructon was necessary for the incident flight and the commander stated that he had ntended the passenger to use “as much oxygen as they felt necessary”. The operator also stated that the oxygen system was servceable and had been used on recent flights. There had been no noticeable leakage from the system and there was more than sufficient oxygen remaining for the planned flight. For the takeoff at 855 hrs, the passenger was seated mmedately behnd the commander n a seat facng aft. As the arcraft clmbed through 0,000 ft, the passenger was nstructed to move to the rear of the cabn, to optmse the arcraft’s CG poston, and to actvate the oxygen system. When seated at the rear of the cabn, the oxygen and ntercom leads were too short to allow hm to connect both smultaneously. Durng the clmb, the commander used hs oxygen mask ntermttently, albet more frequently as alttude ncreased. When not usng the mask, he placed t on hs lap. Once level at FL20 n the cruse, he engaged the autoplot. Durng the subsequent cruse, the passenger had the mpresson that the commander’s voce was “a lttle slurred” when transmttng to ATC. When asked, the commander confirmed that he was using oxygen and shortly afterwards he was seen to be adjustng the engne controls. The commander subsequently confirmed that he took off hs oxygen mask to adjust the controls n response to a perceved engne problem. Soon after, the passenger heard a change n engne nose and was aware of vbraton together wth the sensaton that he was beng pushed nto hs seat. Attempts to contact the commander by ntercom were unsuccessful and, wth the arcraft descendng at hgh speed and n a spral, the passenger called twce for the commander to transmt a ‘MAYDAY’. The commander responded to the second call and declared an emergency. The arcraft was stll descendng and, at around 5,000 feet alttude the passenger opened the emergency escape hatch n preparaton for a possble sea dtchng. However, the commander then reganed control of the arcraft and once t was fully stable, he requested a dverson to Amlcar Cabral Arport on the Cape Verde Islands. A safe landng was made there at 2005 hrs. Post landing actions After landng, the commander checked the arcraft and considered that it was fully serviceable. He was confident that the arcraft had remaned wthn normal operatng parameters durng the ncdent and that no negatve ‘g’ manoeuvres had occurred. On reflection, he considered that he had started sufferng from hypoxa durng the clmb. The perceved engne problem probably resulted from hm not correctly adjustng the engne controls at alttude. The commander contacted hs company engneer n UK to advse hm of the ncdent and also carred out uneventful engne ground runs the next day before 48 © Crown copyrght 2007

Show full text

AAIB Bulletin: 6/2007 G-OOSI EW/A2006/12/02 flying the aircraft to Dakar Airport in daylight. At Dakar, the company engineer, who had flown out from the UK, checked the arcraft and assessed t as fully servceable. The arcraft’s oxygen contents gauge was readng 600 ps. Cessna 404 oxygen system If an oxygen system is factory-fitted to a Cessna 404, the storage cylnder(s) are normally carred n the nose compartment. It s actvated by the plot pullng the oxygen control knob to the ON poston allowng oxygen to flow from the regulator to all cabin outlets. However, the cabin of G-OOSI had been significantly modified for survey tasks and an oxygen cylinder was nstalled at the rear of the fuselage. The oxygen control knob was located at the rear of the arcraft cabn. Consequently, the commander had ether to actvate the oxygen system before takeoff or nstruct passengers to actvate t n the ar when oxygen was requred. A normally closed valve n each oxygen outlet s opened by nsertng the connector of a mask and hose assembly. The front-seat oxygen outlet was under the armrest besde the commander’s seat, adjacent to the headphone and mcrophone jack sockets. The passengers’ oxygen connector at the rear of the cabn was above hs head wthn a small panel contanng lghts and a ventlaton outlet. Ths panel dd not have adjacent headphone and mcrophone jack sockets. The Plot’s Operatng Handbook contans an arcraft alttude operatng lmtaton of 0,000 ft wth oxygen equpment. Regulations All aircraft must fly at an altitude less than 10,000 ft unless the arcraft has a pressursed cabn or the plot uses an ndvdual oxygen source suppled by a personal mask. Addtonally, t s recommended that oxygen be used at a lower altitude when flying at night. Pilot’s assessment After the ncdent, the plot stated that although he was aware of the nsdous nature of hypoxa, and despte hs attempts to recognise the symptoms during the flight, he under-estmated the rsks of becomng hypoxc through not wearng the oxygen mask contnuously. Company actions The company concluded that the man contrbutng factor to the ncdent was the commander not usng hs oxygen mask contnuously above 0,000 ft. Another contrbutng factor was that at least one of the oxygen masks on the arcraft may have had a defectve mcrophone; ths would have requred the user to remove the mask when communcatng wth ATC. The company ntends to mplement more strngent hypoxa tranng and s also makng the followng changes to ther procedures: 1. Future annual flight checks for all company pilots will include a briefing on the use of the arcraft oxygen system. 2. When operatng abroad, crews wll be requred to nform the Chef Plot or Company Safety Plot whenever equpment s unservceable. . Camera operators wll be requred to attend ntal company CRM courses. 4. Night flights in unpressurised aircraft will be prohbted above 0,000 ft. In vew of these actons, the AAIB dd not make any safety recommendatons.