Sorry, But you are not approved as our Member. We will contact you ASAP.

MAST – 17th June 2009 – Heathrow Meeting

MAST Meeting – Heathrow – 17 June 2009
CE Meeting Summary

AGENDA

ITEM 2 – REVIEW LAST MEETING ACTIONS

  • Pushback WG – Need to continue to remind crews of the new pushback arrangements and that pilots can expect a challenge from the tug crew if any misunderstandings on clearances. The feedback form to report pushback problems are widely available at Heathrow now.
  • Airfield driving offences are now being co-ordinated between police and BAA
  • All Runway Incursion info should be sent into NATS/BAA for co-ordination.
  • An old signage DVD was considered out dated, therefore NATS are looking at putting together a road show on signage for all airlines operating at LHR
  • Met offering driver skid pan training at Hendon for selected driver tasks
  • Top 3 safety Issues at LHR from the airlines requested for the next meeting

FEEDBACK

  • BAA
    • Japan Airline incident involving baggage container ingestion highlighted
  • UKFSC
    • Use of Runway Ahead markings – CAA policy on use was briefed and discussed by the meeting. The following actions agreed as a result:
    • Feedback to be sought from pilots and airfields drivers on where these signs would be most effective
    • The next LHR van run will be used to identify the possible positions for the markings
    • A NOTAM raising awareness to be issued highlighting that new markings will only occur in specific hotspot areas
    • A NATS human factors assessment of the impact will be considered
    • Feedback from the Eurocontrol Workshop on runway status lights and stopbar use policy held on 29 April 2009
    • CAA Policy on marking hotspots on charts was re-iterated and why!
  • NATS
    • Navtech chart makers will visit LHR tower to talk charts and plates on 24 June 2009
    • Vancouver airport hotspot website demonstrated

SAFETY REPORTS

  • One Cat D Runway Incursion at LHR in May – vehicle cleared onto runway when an aircraft was cleared to land. In fact, the vehicle vacated the  RW before the aircraft landed
  • Actions taken in response to previous RIs this year
    • De-icing incursions in Jan – awareness training now introduced into de- Action to reduce complex situations for controllers by issuing further guidance- this was in response to an error in line up clearance given to 2 aircraft out of sequence almost simultaneously
    • Incident 906 in Feb. On being given the expectation of a late clearance, an ac was instructed to ‘go round’ instead but replied ‘clear to land’ – and did so without clearance. The controller allowed the aircraft to continue to land after re-assessing since the conflict had been resolved
      • A very useful exchange of views between ATC and pilots followed which concluded that the ATC must explain why a late clearance is to raise situational awareness in the cockpit and not to raise expectation
    • Incident  in June where a possible RI (under investigation) was cleared to land with the runway inspection ongoing – the inspector vehicle turned off prior to ac coming into close proximity. Long discussion ensued on the lessons from this incident – requirement identified to build up situational awareness in the mind of the pilot when and why a late landing clearance is given – do not raise expectations of landing
      • Di-identified lessons will be distributed on completion of the investigation
  • Incident in March – Two intruders onto RW 09R apprehended by the police
  • Ac crossed the stopbar without clearance during controller switchover and entered the RW with another ac cleared to land. Incurring ac instructed to cross runway and expedite on taxiway .Having crossed, ac did an unauthorised 180 turn inside the stopbars and the runway and held off for approaching ac to land
  • Another incident in June involved a A321 lining up without clearance on 09R with another ac on approach – caused through lots of HF including distraction, expectation, change of situation with the checks, misident of approaching ac intent with northerly wind all combined to an incursion.
    • Another ac behind saw the confliction and called it to ATC – action taken to move incursion ac off the runway prior to the landing and alerted the ATC. RI resolved by instructing incur ac to depart the runway at next available turnoff – approaching ac landed safely

SAFETY PERFORMANCE INDICATORS – DATA GATHERING

  • Next Pushback WG on 20 June 09 will undertake an incident review and Gatwick NATS will brief on their pushback communications trial
  • A Scratchpad investigation on taxing routeing errors at LHR is starting in 2 weeks to identify further problem areas
  • In light of the success of the first Operators Van Run, a similar Drivers’ Van Run will be undertaken next.
    • The next pilots Van Run is in the Autumn
  • Safety Performance KPI values will be reviewed for next meeting

LHR MAST WEBSITE

  • A dedicated LHR MAST Website to provide information for LHR users is being proposed, for use by both ground and air operators.
  • It will feature maps/error hotspots/runway incursion/ATC forum/signage
  • The website will be for information only – it will be made clear that the authoritative reference sources are the authoritative  source of data
    • The possibility of including information relevant to specific aircraft type was requested as an aid for those pilots flying in for the first time

BAA (HAL) HEATHROW WEBSITE

  • Official BAA LHR Website is being developed for posting in the next month
  • Operational Safety Instructions for drivers and other airfield users will be recorded supported by automatic update emails
  • Ground handling incidents will be registered centrally and shared with all contributors and published behind secure password protection
  • The MAST Intent is to include the MAST site as a part of this BAA/HAL site

AIRFIELD DRIVING NOTIFICATIONS

  • Vehicle accidents and incidents –prime driving infringements at Heathrow ground remain driving whilst using a mobile phone and driving without due care

AOB

  • There is still a vast quantity of rubbish and waste being abandoned across the airside area. Foxes scavenging is now a major issue at Heathrow
  • MOR Details from the CAA – the current KPI list plus the TOP 10 most common incidents at LHR will be sought from the SIDD at SRG.
  • NATS Policy on use of CAT III holds is being developed and will be issued shortly

Next meeting 19 Aug 09 followed by 14 Oct 09 then 16 Dec 09

Rich Jones
Chief Executive
UKFSC
19 June 2009

MAST – 19 August 2009 – Heathrow Meeting

MAST Meeting – Compass Centre, Heathrow – 19 August 2009
CE Meeting Summary

AGENDA

ITEM 2. MINUTES (June 2009) AND CONCERNS AND COUNTERMEASURE SHEET

  • 32 – ASMGCS link to EFPS to AGL – this is a long term project
  • 44 – Driver training still on offer by the LHR Police
  • 45 – Chocking of aircraft is recommended under the LHR OSI – not mandated!
    • Two ac have rolled in the past week!
    • BAA states that it is the ground handler company and airlines responsibility to ensure adequate chocking is undertaken
  • 49 – A top safety issue is an inability to provide sufficient notice of work in progress on the airport to the airlines-another solutions are being investigated
    • An advanced info booklet which detailed the work plan was offered as an idea – UKFSC CE to contact EAG
  • 53 – ‘Runway Ahead’ warning signage issue was discussed – A trial now underway but further HR investigation may be needed – UKFSC CE to seek the CAA work for the MAST
  • 59 – RWSL workshop on introduction in Europe discussed. NATS will meet with Eurocontrol in September on this issue
  • Heathrow is being asked to undertake an RSWL trial
  • A separate contract by Eurocontrol has been issued to NATS to investigate RWSL application

FEEDBACK

  • RW Warning Signage policy was meeting with resistance amongst other bodies. Debate revolves around having the signs at every intersection or just hotspots
  • Pushbacks – still some confusion on request and approval responsibilities with the new system. PB WG needs to decide on a standard approach to PB requesting and then publish this to all players

SAFETY REPORT

  • Runway Incursions
    • No incursions this month
  • Latest CAA Review of Runway Incursion Info to be distributed to MAST members
  • RIs appear to be going down at large UK airports but up at medium/small airports
  • Driver incursions is a growing concern

SAFETY KPI REVIEW

  • 2 unauthorised pushbacks in July
  • 4 Cat A-C RIs in 2009 so far whilst only 2 in 2008
  • 2 Ground Collisions this year

EXCURSIONS

  • CAA is undertaking a major piece of work on runway excursions – a Task Force is chaired by James Eales
  • CAA is seeking feedback from the BAA to stimulate discussion
  • Causal factors and categories for RW Excursions have been identified and circulated to MAST
    • These will be provided in the MAST Minutes

MAST ACTION PLAN

  • RWSL – a sub group to consider this issue has been established
  • NATS – CAA HF analysis of the Runway Ahead work – CE to pursue CAA analysis
  • Van Run for drivers will take place in Sept
  • MAST will look further at the CAT 1/2/3 hold issue at the next MAST meeting
  • Pushback WG continues to work on unauthorised PBs
    • More pilot input to the PB WG is requested
    • Debate about the GMC wording by NATS/pilot/tug. The issue to be looked at by the NATS/BMI Reps at PB WG and report back to MAST
    • Datalink – may provide a future solution – under SESAR?
  • Transponder fitting for vehicles is being investigated
  • The BAA LHR Website is now on line and dedicated MAST input now requires consideration
    • Dissemination of error hotspots
    • Consultation on what pilots would wish to see
  • Driver training using simulation is now being developed for LHR drivers

BAA LHR AIRSIDE WEB SITE UPDATE

  • BAA website has now gone live, and includes links to other info
    • Comment requested from MAST Members on current content
    • MAST will have a dedicated input to this website
    • Subscription, security and access is now under consideration

TECHNOLOGY

  • UKFSC CE provided an update on Manchester radio trial and Bournemouth rumble strip and on the latest RISG output

AOB

  • UKFSC CE briefed on the CAA Significant Seven Task Forces – Chair requested an update at the next MAST
  • GAP – FSF – Best practice videos for ground operations practices and towing of business aircraft now available on line at http://www.flightsafety.org/gap.html
  • A rare back-lighting fault on a stand guidance system (on stand 409) caused a serious ground collision incident
  • The ac overshot by 3 metres causing a collision with ground equipment and damage to the aircraft engine pod
  • A long term major review of the Airside Works Approval process – aim is to be more efficient at undertaking this work and less disruptive to operators
  • NATS will undertake an Ops Safety Roadshow for LHR based airlines in Sept
  • A11 Intersection at LHR has had 2 RIs this year – suggestions for signage discussed – but this needs further detailed HR analysis before a definitive recommendation could be made by MAST
    • The next Van Run could consider this problem
  • UKFSC CE briefed on the Lasers situation and on the SBAC Code of Practice being developed for ‘taxi on less than all engines’

Next meetings – 14 Oct / 16 Dec 09

Rich Jones
Chief Exec
UKFSC
21 August 2009

European Society of Air Safety Investigators Seminar (ESASI) – 23rd/24th April 2014 – Milan

European Society of Air Safety Investigators – Regional Seminar 23/24 April 2014
CE Report

This 2 day seminar was held in Milan under the Chairmanship of Keith Conradi, Chief Inspector of Accidents AAIB and ESASI President; there was a broad range of delegates from Europe, the USA and Japan.

Constructive Co-operation in EU Accident Investigation – Luigi Candiani (Augusta Westland)

The first presentation examined some of the lessons learned from investigating accidents under the Italian legal system. Italian investigations usually involve a public prosecutor who is obliged to carry out a parallel investigation in the event of deaths or injuries. Magistrates focus on finding guilt rather than causation; an ‘aviation culpable disaster’ involving death or property damage to 3rd parties can incur a 12 year maximum jail term. The public prosecutors are appointed regionally and may therefore be investigating an aircraft accident for the first time. Investigators in Charge can be called to testify at trials as a person informed on the facts. The Italian AIB (Agenzia Nazionale per la Sicurezza del Volo) is under the direct supervision of the President of the Council of Ministers and not the Minister of Infrastructure and Transport (who owns the CAA).

Case study on co-operation:

An AW109 on an EMS flight crashed into the sea at night in Nov 2007. All survived but there was no pre-impact RT, which delayed the rescue effort. The aircraft was in a descent when it experienced high levels of vibration and shaking; application of collective at 100ft led to a low-speed impact but the helicopter rapidly capsized. It came to rest inverted but intact on the sea bed at a depth of 105m, close to the working limit for divers.

Discussions with the manufacturer (AW) indicated the best means of lifting the wreckage was via the undercarriage as there was concern about the integrity of the main rotor gearbox. The aircraft was lifted inverted into shallow water where the rotor blades were removed and the fuselage rolled upright using strops. Once on deck (about 6 months after the accident) the wreckage was immediately washed with fresh water and non-volatile memory items were immersed in clean water. By agreement with the public prosecutor the Italian Air Force conducted the inspection and analysis of the wreckage. Agreement was also required for chip cloning and data retrieval from the Data Acquisition Unit, and a successful download was achieved despite a 6-month salt water immersion.

Lessons learned: The collaborative/co-operative approach to this investigation was possible under Reg (EU) 996/2010. FDR and CVR should be fitted to all (commercial) aircraft under 27 tons, NAAs should encourage this and manufacturers should include this in their proposals to customers. FDM for lighter aircraft should be considered. FDR data needed to encompass control outputs not just inputs.

EASA NPA 2013-26: Requirements for Flight Recorders and Underwater Location Devices – Guillaum Aigoin (EASA)

The AF447 experience had prompted ICAO to update its requirements for FDR, CVR and ULDs. There were 4 issues: obsolete recording technology; CVR over-writing; ULD transmission time; and location in oceanic areas.

Many FDR and CVR were still using magnetic tapes or other ‘old’ media, and data was either missing or of poor quality in a 1/3 of all accidents and incidents. 30% of the CAT fleet (EASA MS) were still using magnetic tape and the rate of replacement was tied to the rate of fleet renewal. ICAO Annex 6 now seeks to phase out obsolete recorders by 2016 and take advantage of the increased reliability and accuracy of solid-state technology.

CVR over-run was a particular problem for incident, rather than accident, investigation. Crews often failed to deactivate the recorders to preserve data, or maintenance staff inadvertently reactivated them. This problem mainly affected large aeroplanes as few helicopters are fitted with CVRs. There have been 7 Safety Recommendations made to EASA on the subject, and 38 CVR over-runs had been reported from incident investigations. ICAO Annex 6 will require CVRs to have a minimum duration of 2 hours by 2016.

Transmission time of ULDs was insufficient at 30 days and ICAO was extending this to 90 days. ULDs with this capacity were already commercially available, and only cost around €500 more than the 30 day variants.

Locating accident sites in oceanic areas with flight tracking was very expensive and, obviously, no wreckage = no proper investigation. ICAO was mandating new long-range ULDs that would transmit on 8.8KHz; this measure would only be applicable to large CAT aircraft.

The EASA NPA has been out for consultation but the recent MH370 accident has led EASA to short-circuit the process and an Opinion will be issued to the European Commission in May/June 2014. The main provisions are:

FDR – Mandated pre-flight checks and obsolete recording media to be replaced with solid-state media by 2019.

CVR – Mandated protection procedures to be included in Flight ops Manuals; Minimum 2 hour recorders to be retrofitted to all commercial air transport aircraft by 2019; CVRs manufactured from 2019 must have 15 hours recording time.

Underwater Location Devices – Must be able to transmit for 90 days by 2020. Large commercial air transport aircraft built after 2005 to be retrofitted by 2019 with a long-range (8.8KHz) ULD or other means to locate the point of impact to within 6nm.

Regulation (EU) 996/2010 Review – Olivier Ferrante (EC)

Article 24 of the Reg requires its review by Dec 2014 and a questionnaire had therefore been sent to all EASA MS and a wide range of other stakeholders. Responses had indicated that the scope and overall functioning of 996/2010 was satisfactory but that some improvements could be made. Over half of the State Investigating Authorities (AAIB etc) either needed assistance or were unable to conduct their own investigations. Dealings with judicial authorities were variable across EASA MS, and there was a divergence on disclosure of sensitive safety information; most SIA had no problems with access to safety information but relevant medical information could be much harder to obtain. Article 21 (assistance to victims) needed improved guidance material and there was a proposal to move it (and Art 20) to other legislation.

EC long-term aim was to generate a central AIB, but all feedback suggests it is too soon to consider this now. Improved co-operation between SIAs would reap benefits in the short term. Work to align MS judicial processes could be protracted.

Co-ordination of Investigations for Similar Events – Mario Colavita (ANSV)

The ANSV recognized that there would be benefit in the timely sharing of information by SIAs between investigations into similar occurrences

An AW139 had ditched in Hong Kong in July 2010. The investigation was ongoing (with ANSV as AcRep for State of Manufacture) when 2 similar events occurred, a tail-rotor failure on the ground in Qatar (May 2011) and a fatal TR failure in flight in Brazil (August 2011). In the Qatar incident, a TR blade had detached followed by TR separation and a pylon fire; ANSV and EASA were members of the investigation committee (which was not Annex 13-compliant), and ANSV was also involved in the Brazil investigation. All events had been sudden with no prior indications of failure.

The Hong Kong CAD made an initial request for co-ordination, which ANSV offered to manage. A joint/multilateral meeting was held in Rome after the 3rd accident, which allowed all 3 investigations to reach a common understanding and alignment of activities. The analysis of the failed TR blades in Italy showed static overload failure of the blade trailing edge bottom strap and some fatigue damage. There were no quality issues and all blades were within design tolerances but there was evidence of weak bonding in the blade root area; new blades have since been certified. The Hong Kong final report is now due for publication, and the Brazil final report is expected in Q3/2014.

The co-operative approach was used again by ANSV in support of the investigations into ATR42 and ATR72 in-flight fire events, of which 3 had occurred in a 4-month period. ANSV acted as co-ordinator for the Denmark and Italy events and was the AcRep for the Bucharest event. The joint investigation found all events were due to failure of a PT1 rotor blade caused by casting defects and subsequent low-cycle fatigue damage. The teams devised short and long term targets including inspection of all pre-2008 blades and improved smoke evacuation procedures. The harmonised EU approach led to 5 joint Safety Recommendations; the reports were signed by the heads of the 3 SIA and published under a cover note by the head of the ANSV.

Small UAS for Accident Site Imaging – Stuart Hawkins (AAIB)

Police and SAR helicopter (or other platform) imagery provides good coverage of accident sites but is not always available and can’t be reviewed on-site. Commercial helicopters cost in excess of €500 per hour and are also not readily available. Commercial UAS provide high resolution and real-time imagery, and are useful for close-ups; however, costs are high (€3000/day) and availability can also be an issue.

The AAIB has been conducting a trial with a small UAS (Phantom 2 Vision) which has all the advantages of a commercial system but at a fraction of the cost (€960 to purchase). The system comes with a 14MP camera and, at <20kg, is quick and easy to deploy. AAIB ops comply with CAA regulations for small UAS, which means special clearance is required for operating in congested areas or above 400ft agl. There are some minor drawbacks with camera stabilisation and remote zoom, though this can be achieved by physically flying the system closer to the target.

AAIB limits its ops to winds

Case Study: MALEV Hypoxia Incident (HA-LOK) 23 Nov 2011 – Janos Eszes (TSB Hungary)

The incident occurred when an experienced B737 crew mis-managed the pressurisation system, leading to the pax O2 masks deploying during the climb. Main causes of insufficient cabin pressure for any aircraft are leaks, inadequate air supply and control error.

The B737 conditioning system has left and right distribution packs controlled by a 3-position switch (OFF/AUTO/HIGH). The crew failed to recognise that the switch was in the OFF position during checklist readouts, one by each pilot. When the warning horn activated during the climb, neither pilot recognised the reason for the horn, ie that it was a pressurisation warning, and the crew then failed to follow the CABIN ALT WNG/RAPID DEPRESSURIZATION checklist.

The Capt silenced the horn after 30 secs and 1 minute later started to level off. At this stage the aircraft reached its max altitude of 17,250ft, the cabin alt reached 14,000ft and the pax masks deployed. The Capt rejected the FO’s suggestion of an emergency descent but neither pilot checked the overhead panel. 2 minutes later, the Capt told the FO there was no need to don their O2 masks and 30 seconds after that he ran the AUTO FAIL checklist, at which stage the packs were switched to AUTO. The Capt then decided to descend to 12,000ft (an action he could not later explain), but eventually descended further, the aircraft and cabin altitude reaching 10,000ft 12 minutes after the initial warning. The crew then held for a while to avoid an overweight landing even though the aircraft was already below this weight at take-off.

The investigation found no technical defects and concentrated on the HF aspects. The Capt was known to be ‘very confident’ and had experienced a similar incident with a technical problem around 2 years previously. He also had a second job and was regularly tired at work, and he had taken a mobile call during the pre-flt checks. The investigation questioned whether some of the crew actions were a result of hypoxia; crew reactions during the approach were very slow and they had failed to complete all the checklists prior to touchdown.

The investigation produced several Safety Recommendations: that the HU CAA required operators to provide realistic training for cabin pressure loss; for the FAA and EASA to introduce alerts for an inactive pressurisation system, and provide alternative actions in the AFM and checklists for pressurisation problems; and that ICAO requires the inclusion of cabin pressurisation in FDR data.

Crew Monitoring – Frederic Combes (Airbus)

This presentation began with the observations that monitoring is not a natural activity, it does not stand alone and is not specifically trained. Slow changes are not attention getters and the risk of an unwanted aircraft state increases if both pilots become involved in non-monitoring tasks. Case studies were then used to illustrate instances of poor and good monitoring. These included an A321 incident where the Alpha-floor protection operated approximately one minute after the aircraft had been levelled at 4000ft with idle thrust selected and the ATHR disengaged; airspeed had been allowed to decay to VLS -26Kts, with the crew still trying to pitch the nose up when the protections activated. Poor monitoring of AP mode annunciation was a feature of this incident and another example given (A310).

In an example of better monitoring, an A330 suffered a RH engine surge at 112 kts on take-off. The FO (PF) achieved 95% rudder deflection within 0.8 secs and the Capt (PM) called the Reject 0.2 secs later; max deviation from the runway centreline was only 3.7m.

Airbus strategies for improved monitoring and situational awareness included:
– Review task in advance, anticipate
– Recognise multi-task demands and allocate areas for attention
– Share perceptions
– Manage workload
– Mentally fly the aircraft even when the AP is on
– Adapt monitoring to the speed of evolution of information
– What if…
– Assign monitoring tasks with at least an equal priority to other flight deck tasks

Runway over-runs – Mark Smith (Boeing)

The runway over-run picture has been getting worse over the last 20 years (357 from 1992-2001 compared with 973 for 2002-2011). Boeing had been conducting Runway Track Analysis using data combined from multiple sources, including time-based FDR to calculate landing positions and energy levels. The primary factors were touchdown point and speed (both variables fixed at touchdown) and deceleration. Results were presented in spreadsheet format.

Of note, 2/3 of all over-runs) were from stable approaches (sample size 39). However, the bulk of the hull losses followed unstable approaches. (Deduction: a stable approach does not guarantee you will avoid an over-run, but an unstable approach markedly increases the probability of a hull loss in the event of an over-run.) Long landings were the biggest causal factor in over-runs. Boeing advice: Land in the first 3000ft (or first 3rd) of the runway, or Go Around. Contributors to long landings included poor flightpath control (high) and delayed thrust reduction. Many fast touchdowns resulted from crews ‘ducking under’ the normal glideslope.

Some over-runs had occurred through poor use of deceleration controls, with crews delaying TR use and/or failing to use the available wheel-braking. Immediate selection of TR meant that full TR could be achieved after about 5 seconds, whereas a delay allowed engines to reduce below flight idle and thereby increasing the selection-full time to 11 seconds or more. Correct use of TR added the same deceleration effect as full braking on a MED runway (ie TR + brakes was double the effectiveness of brakes alone). Runway condition was seen as a contributor rather than a causal factor, but this also meant that good runway conditions could be masking potential over-runs. Use TR until 80 kts or until stopping is assured.

Linking Air Safety Investigations – Leonardo Ferrero

This short presentation covered the work of a student who has developed a search engine for aviation accidents that links a number of existing databases and creates a virtual library. It also has a ‘find similar’ button that aligns different taxonomies. The resource links to the FAA lessons learned library (http://lessonslearned.faa.gov) ASN and SKYbrary; the FAA resource lists 71 key accidents, grouped by themes. You can find the website at www.linkingASI.eu

Investigating Air Accidents in an Urban Environment – Sid Hawkins (AAIB)

This interesting presentation looked at the initial AAIB response to the helicopter accidents in Vauxhall and Glasgow in 2013. The Vauxhall accident was pictured on Twitter within 2 minutes of the event; traffic congestion hampered arrival of the advance party (on site @ +3 hrs) and the main recovery parties subsequently had a ‘blue light’ escort. Emergency services declared a major incident early in the process, which meant Silver command was established just off-site; AAIB has identified the need to have a permanent presence at Silver level when this form of command is being used. The Police handed control of the site to the AAIB at an early stage, which increased the management task for AAIB, but helpfully also produced a laser scan of the area that helped with wreckage plotting. Insurers and loss adjusters have a legitimate role in the process, which required them to have escorted access to the site. The site was cleared of wreckage and handed back to the emergency services 33 hrs post-crash.

The Glasgow event occurred late at night and the AAIB was not on-site until the next morning. The accident generated political and international interest which included the presence of the Scottish Deputy First Minister at an on-site meeting. The Police delegated control of the site jointly to the Fire Service and AAIB, reflecting the dangerous condition of the wreckage and building. Priorities (set by the Police) were safe ops, dignified recovery of the deceased, and recovery of evidence. Removal of the wreckage was undertaken in full public view, with only one chance to ‘get it right’. Lessons included the need for on-site storage and site security. The location was released by AAIB after 54 hrs on site.

————–

Copies of the presentations will be made available via the ESASI website and will be transferred to the UKSFC where possible.

Dai Whittingham
Chief Executive
15 May 2014

IATA Incident Review Meeting – 10/11 May 2011 – Geneva Meeting

IATA Incident Review Meeting 10/11 May 2011 – Geneva

Confidentiality -Please feel free use this information within your company but DO NOT mention that it was gleaned at an IATA Meeting- otherwise access to future information could be denied.

Global Safety Update

  • Total fatal accidents in 2011 is 23 so far against 35 in 2010
  • Fatalities in 2010 was 760 against685 in 2009
  • LOC was the top contributor for fatalities in 2010
  • Runway Excursion was the most prevalent
  • Ac technical faults caused 10% of accidents in 2010
  • 88% of accidents identified deficiencies in Operators’ safety management
  • LOC accidents are trending level for past 3 years
  • CFIT accidents trending slightly up

SPECIFIC INCIDENTS

A319 Stall on the Approach

  • A319 on ILS with AP/FD and AT engaged
  • Weather was indicating poor with TS and strong gusting winds; several ac had decided to divert based on weather
  • Ac was stable at 1800’ with a 10-13 kt tailwind
  • Between 1800 and 1700, a 10 kt down draft hit the ac and it pitched 15degrees and went to 15AOA and speed speed warning triggered
  • At 1670’, a 23kt down draft hit, CAS went to 116 kts and the AT commanded climb power tailwind went to 35 kts
  • At 1620’, the ac pitched up 33 degrees and had AOA of 25. AP/AT disconnected
  • Stall warning triggered and AOA went to 32 degrees
  • Protection provided full nose down to counter stall
  • Both crew tried to pull nose up using back stick to no avail
  • Conclusions
    • Consider delaying landing until better weather
    • Consider diverting
    • If landing:
      • Apply FCOM advice- Adverse weather and wind shear
      • Closely monitor parameters and cal out deviations
      • Respond immediately to wind shear or low energy state
    • Improve crew wind shear awareness and prepare them to take over!

Stall Recovery Training

  • Standard Stall recovery Procedures and Trg Brief already briefed to UKFSC
  • Airbus experience is that A380 stall at 12000 needs 1800’ to recover
  • ………………………………….A 320 stall at 12000 needs 1200’ to recover

B747 Upset In Severe Turbulence

  • Summary – B747 freighter in the cruise at FL250 Ac in autopilot was unable to maintain level flt and started climb to FL327 within 1 minute – overspeed warning and stick shaker occurred before PIC took control
  • Flt plan restricted to FL 250 due to radiation cloud over Tokyo but did not take into account the turbulence or WS threat.
  • At FL250, speed increased from 318 to 331 triggering an overspeed caption
  • Climb rate changed from 1200 ft/sec to 4000 ft/sec within 11 seconds which produced a stick shaker
  • PIC cancelled the autopilot and auto throttle and pushed the stick forward, increased speed and levelled back at FL 250
  • Major cause analysed as WS more careful flight planning would have avoided the area and height at which WS was predicted.

Smoke in the Cabin

  • Cabin crew smelt burning in the cabin on preparing the cabin on the ground
  • A seat cushion was found smouldering and removed from the seat
  • A disposable lighter was trapped under the seat and had been actuated
  • One lighter is still allowed in the hand baggage on this airline
  • Another airline had a similar burning seat problem when airborne
    • They checked under other seats and found more than 40 lighters
  • Should we ban lighters in hand baggage?
  • Another airline reported a crushed iphone battery under a seat which caused a fire
  • A overhead lightwould not turn off – an apple was pushed in the holder it set alight

B737 – 800 to AKJ North Japan Vector Below Mva By Atc

  • ATC vectored towards 9000’ high ground having cleared ac to descend to 5000 EGPWs sounded twice pilot pulled up as required and cleared grd by 710 ft
  • VSD on ac indicated high ground before EPGWS
  • Why did ATC issue a radar vector below MVA?
  • Crew tried to contact ATC before warning but failed due to contact due to other transmissions
  • ‘It may not be sensible to have too much confidence in ATC’
  • MVA chart carriage was discussed One airline at leasthas stopped carrying them due to they being too confusing and cluttered for the pilot
  • MSA is the standard used to judge minimum descent altitude policy on descending below MSA What do airlines do?

CFIT In Cold Atmosphere

  • GPWS on offset final in low temp
  • AOMON fltwith strong wind and temp at -8 degrees
  • GPWS calls caused by bad weather, nav mode and map unreliable after mods
  • Strong wind effects
  • Use of temperature corrections to altitudes raised as per the Manchester case

TCAS Encounter

  • Feb 11 An Airbus descending to FL 80 inbound Htw and an Emb on climb out from City cleared FL90
  • Both heading into Lambourne
  • On climb out, ATC received a STCA alert and tells Emb to stop its climb
  • Exactly at the same time, TCAS provides an RA climb instruction to the Emb which he follows, and the Airbus has a descend instruction from TCAS.
  • Soon after the Emb gets a TCAS reversal
  • Both pilots had visual but this would have proved to be of no value since the Airbus Captain gave the wrong instruction to co-pilot to the TCAS instruction as a result.
    • The co-pilot followed the TCAS not the Captain!
  • 1.4 nms and 200 ft sep at nearest point if reversal had not been taken, a collision was considered highly likely
  • The investigation found that the companies Ops Manuals were incorrect TCAS instructions and the training provided were inconsistent use of the visual was allowed in the Manual but not trained in practice this has been addressed.

Accidents And Incidents 2010 – BoeingBob Aaron

Air India Express Magalore Accident

  • Prior to flight, the Captain on days off with sore throat
  • Crew had sufficient rest according to the schedule??
  • Minor MEL issues dealt with prior to take-off
  • Mangalore is a table top runway with severe drops either end
  • Captain was sleeping for at least 1hour 40 mins of the flight
  • Capt had landed 16 times before and co pilot 66 times at Mangalore
  • No specialist briefings for the landing undertaken
  • High and fast on descent and approach with12 degrees down on going through glideslope
  • Sleep inertia of Capt after deep sleep longer than 40 minutes max,it can take a few minutes to 4 hours to come around properly
    • Core body temp was very low
  • No descent profile properly planned or flown
  • 8000 foot runway- touchdown 5200 down from the touchdown with 2800 left
  • Started a go round very late
  • Wing hit an ILS ground base and boundary fence and went down the slope
  • Final report on website Conclusions are:
    • Unstabilised approach
    • FO called go-round 3 times not actioned by Captain
    • No coms or in harmony on the flight deck
    • Major trans cockpit authority gradient
    • CRM failure between Capt and the FO
    • CRM training in airline needed
    • Multi-cultural lessons
    • Indications of a false glideslope

Recent Georgian CRJ 100 Landing accident Kinshasa, DRC

  • ADRs sent back to France for analysis
  • Hi impact crash wide of the runway total destruction
  • No further information

Near Runway Excursion on Contaminated RW at Moscow

  • Moscow RW 32 approach at night with light turbulence and light winds
  • At 300 ft, a crosswind of 250/36 kts developed
  • Landing on touchdown point and speed OK but on roll out, Captain unable to control the ground direction due to poor braking action on final phase of the rollout
  • In fact, the 1 mm of contamination reported was causing less than 25% of braking action available
  • This poor quality of reporting of runway friction appears to be a problem at other airports in Russia incorrector inaccurate braking action reporting

Air France Collision At JFKNot Published Yet

  • A380 Crew taxied out a 10 kts on ground clearance
  • Informed of traffic at far end of KD taxiway
  • CRJ700 was stopped having turned off the KD taxiway awaiting entry to the ramp
  • NOTE The YouTube Video is twice the speed of reality
  • Left wing box plus slats damaged on the A380
  • CRJ is severely damaged possible write-off
  • Media interest significant NTSB investigation
  • Air France action
    • Interview crew
    • Sim check
    • No further action taken until report is issued
  • Similar Madrid event- B747 and DC9 tail and rudder removed
  • Increasing concern for the future more wide wing spans, winglets, carbon fibre based, congested ramp 70% for traffic with no new airports
  • Quick survey of incidents found that wing tip strike events are:
    • Numerous,ac on ac
    • De-ice facility hits
    • Ramp pier hits
    • B747 hit the Presidents MD 80 on congested ramp
      • near crew imprisonment
    • These can happen at good airports
    • Many cases where pilots adjusted their position but still hit
    • Good compliance is to stop if you are not sure- this is the commonsense fix!
    • Ground safety initiatives are failing to address this issue
    • Commonsense rule that pilot is accountable does not help engage the others who can assist the pilot in addressing the problem
    • Damage with ac to ac is 28 times more expensive than vehicle hit
    • Trinity College Dublin has a WingWatch AC grd collision avoidance system on trial

AC Ground Rollback Events

  • Numerous rollback events are taking place around the world
  • Typical events at Heathrow
    • B777 rolled back when hand brake stopped working correctly
    • A320 rolled back due to loss of pressure on the brake system
  • Between 2005 2009 there were 5 roll back events
  • In 2010/11 one airline had 11 events!
  • Chocks procedures not meeting the requirement/or the problem is not understood
    • A internal airline review is being undertaken using bowtie analysis
  • Other airlines were invited to share best practice
    • New airports in the Far East have significant slopes due to drainage requirement, so parking brakes and chocks are essential
    • Many airports require the wheels to be chocked and brake off before they will service the ac. (Some airlines make no exceptions to allow crews to park with the brake off)
    • Heat dissipation is another Far East concern
    • FAA have been checking chock distances being used at airports since some ground crew leave the chocks some distance away from the wheels for ease of removing the chocks
  • Both Boeing and Airbus say that before the park brake is released, the peddle brakes should be engaged, the park brake is then released, and then the peddle brakes released slowly looking for any ac movement outside

Risk Management Process for Return to Operations A380

  • The A380 was grounded by Qantas in Nov 10
  • 7ac delivered with 6 operational in fleet
  • The incident ac had 5 flt crew, 24 cabin crew and 440 pax
  • Normal take off and climb to 7000’
  • The engine had a disc liberation well known and reported widely
  • The landing and evacuation not so well publicised
  • On landing the No1 engine continued to run for another 2 hours! would not shut down and needed external application of foam flame retardant to stop it.
  • Fuel was pouring from the wing onto the ground making it difficult to get pax off.
  • The Crisis Management Process was activated at Qantas following a planned strategy
  • Social media were on the case immediately which added to the confusion since AAP news agency were reporting an A380 crash
  • Decision taken by Qantas to suspend A380 Operations with 2 about to despatch stopped and one airborne into LA
    • Grounding left 2000 pax stranded at LA
  • A plan to get the ac back in operation was needed and was as follows:
    • Identify threats, defences, controls and consequences
    • Test defences including escalation factors
    • Assess likelihood of reoccurrence and exposure to triggers
  • Recovery Plan then included:
    • Establish technical diary of events
    • Validate OEM advice
    • Test defences
    • Re-assure the regulator
  • Initial Technical Assessment was oil-fed fire leading to IPT disc failure
  • Oil leak caused oil fire which damaged the disc drive
  • The disc drive overspeed and the disc broke up
  • A bowtie method was applied to identify the threats
  • The defences were reviewed and additional defences considered
  • Conclusion was the oil fire was to be prevented
  • CASA then said they would make the final approval decision
  • A crack was found in the oil feeder tube
    • This was found to occur at high thrust levels when the oil pipe was being aged rapidly.
    • Poor manufacturing of the pipe and its layout was the likely cause
    • Tube fit and fatigue where pipe fitted into the casing turned out to be the weak point
  • A pressure sensor could detect these high thrust levels
    • The way ahead was to remove those engines with indications of high thrust engine exposure
    • A AD was issued accordingly
  • What changed?
    • All damaged units were removed from service
    • All Ops to LA were suspended due to higher exposure to high thrust
    • Manufacturer of the oil pipe joint identified that the pipe was too thin around the joint in some cases, due to eccentric boring in manufacture
    • Rupture of the IPT disc drive leads to an overspeed
    • An IPSOS system is being fitted which senses the conditions for an overspeed and shuts the engine down before an overspeed can occur
  • Conclusion
    • You can never train or practice your crisis response team enough
    • Impossible to anticipate every scenario
    • A well practiced framework is helpful

A330 Freighter Fire Incident

  • There are accessibility entries and hatches in the cargo compartments of the A330 to allow crews to identify and deal with fires in a package
  • Any Class C packages must be carried in a fire suppression hold
  • In cases of fire, the SOP is to depressurise the compartment in case of fire
  • However concern expressed about whether the crew should be allowed in these areas in case fire occurs.
  • A comprehensive assessment of the risks is to be carried out.

B737-400 Electrical Incident

  • A B737-400 en route across Borneo had several electrical failures and warnings about 1 hour after take-off, so crew decided to divert
  • A battery failure as suspected.
  • Check list was followed which indicated that the battery was almost flat
  • Multiple fails including standby horizon toppled
  • No cabin PA or warnings available
  • On approach , the landing gear showed 3 reds and 3 greens- a visual approach over the tower was undertaken to check gear status
  • During the go-round the gear was selected up!!!Why???? But the gear stayed down.
  • On landing the reverse thrust failed to landing successful
  • On arrival on stand, the ground crew had no lights available to assist getting the pax off and ac torches had to be used instead.
  • The subsequent investigation found:
    • Non mandatory information from Flt Op tech bulletin had not been disseminated to the pilots
    • The cause of the electrical problems stemmed from the failure of 2 relays on the battery bus
  • This incident prompted another airline to mention a non-mandatory service bulletin which advised the replacement of the inverter resistor on the B757, which the engineers chose to ignore.
    • Subsequently, a fire and evacuation occurred as a result.
    • The B767 has the same fit of inverter resistance type.

Rich Jones
UK Flight Safety Committee
30 May 2011

IATA Incident Review Meeting – 4/5 May 2010 – Canada Meeting

IATA Incident Review Meeting 4/5 May 2010
CE MEETING SUMMARY

THIS MEETING IS HELD UNDER SIMILAR RULE OF CONFIDENTIALITY TO THAT APPLIED TO UKFSC MEETINGS.UKFSC MEMBERS MAY USE THE INFORMATION WITHIN THEIR ORGANSIATIONS BUT ARE ASKED TO RESPECT THE SOURCE MEETING AND DISIDENTIFY INCIDENTS ACCORDINGLY

IATA SAFETY REPORT 2009

  • 2nd Best year for the industry with 18 fatal accidents total
  • IATA carriers lowest level to date
  • Landing is the maximum risk area for accidents
    • Most common at 27% Runway Excursions/2nd – Gear Up landing/ 3rd – hard landings

A330 OVER SPEED Aug 09

  • Severe turbulence Encounter and Roll Oscillations over Bay of Bengal
  • 2.3 hours in at FL400 M0.82 at night
  • Severe isotropic turbulence an overspeed developed
  • Capt was flying FO out of the cockpit
  • 64 degree bank at times but no injuries
  • FDM data shows
    • Rapid wind direction change from east to south- by 24 knots
    • Mach from .818 to .873beyond MMO for 4 secs
    • Speed brakes set after 6 secs after overspeed
    • Auto-pilot was disengaged instinctively
    • Tried to re-engage severally ties unsuccessfully
    • Went into a climb and went low speed to 244 kts up to FL410
    • G went from 0.3G to 1.6G
    • On reengage of autopilot the oscillations stopped quickly
  • Lessons
    • Lap belt only now changed to full strap in when left solo struggled to keep his seat
    • Cabin crew also enters cockpit in jump seat when solo pilot
    • Late at night no evidence of fatigue
    • Contain the startle factor caught by surprise
    • Input very small inputs
    • Changes to sim syllabus for recurring trg for high altitude operations
      • High speed recovery
      • High speed protection demo
      • Low speed protection demo
      • Bank angle protection at 67 degrees

EMBRAER 190 UPSET

  • Level cruise Anchorage to Chicago
    • E190 midair upset through wake turbulence from a B747 on RVSM.
    • E190 had a 1 minute notice to prepare for it
    • (En route RVSM wake turbulence reports are being sought by NATS)

Post Maintenance Flight UKFSC

  • Presentation on UKFSC website
  • FSF one time symposium 26/27 Jan 2011 on post flight maintenance in Vancouver and Singapore

B777 Inadvertent Autopilot Engagement on Ground

  • A B777 departing Tokyo with 296 pax high speed rto – $1.2M in damage
  • Caused by inadvertent autopilot engagement high column forces at rotation twice as much pressure as normal to break the autopilot
  • Nine instances of this occurring and RTO resulting
  • Software change introduced to correct this issue
  • Potential for RE
  • HF related to autopilot location
    • B767 hangover where the action is similar to another switch selection on the MCP but not autopilot!
  • Service letter, Service MOM and FAA AD sent out 1 Apr 2010
  • B747 may have a similar problem it has happened
    • One major airline had an event on take-off when both pilots had to pull together to get airborne

KINGSTON JAMAICA B737-80022 Dec 10

  • Miami to Kingston overrun on landing
  • Offset localiser at this airport using a Head-Up display is more difficult
  • Poor drainage on an intersection and runway did not help
  • FDR showed no problems with gear brakes spoiler or brakes
  • Ac split into 3 pieces after jumping a berm latest 16G seats saved pax
  • Seats all stayed in place bar one which was mis-installed
  • Flight deck took a serious hit
  • Small fuel leak only from right wing
  • Wx on despatch was OK at destination and landing
  • Landed just under max landing weight with a tail wind
  • Landed 4000’ in but everything else was correctly handled
  • New York Newark 22 R has a similar offset localiser which is missed the offset on the chart – no action by Jeppeson so far not much action so far.
    • On airline recorded 2 go rounds caused by confusion with the offset
  • At this stage , EMAS marking on the map was also discussed as another appositive improvement to airport charts
  • ICAO is looking at scoring all runways against the ICAO standard

De-Icing Fluid Application RTO

  • Over 3 winters, 2 RTOs occurred that took a major analysis to understand
  • On S300 take-off, pilots were more cautious on rotate due to additional force being required to pull through the spring rod force on the lift tab on the elevator to break out the de-ice fluid resistance on the control surface.

Runway Collisions And Related Issues

Eurocontrol Evair Data Collection

  • ASRs from airlines 3100 reports with 63 airlines working with EVAIR
  • Feedback from ANSPs 25% replies were received within 1-14 days
  • Other EVAIR actions
    • Madrid action plan and Taxiway Task Force
    • TALPA
    • Cyprus Disputed areas Turkish area is being followed up through ICAO
      • Establish coms between disputed areas data is needed
    • Callsign confusion guidance has now been produced and on the website
    • Laser attacks are growing across wide areas and action is required
    • ACAS
    • Volcanic area
  • Phases of Flight Accident analysis – 2006-2009
    • Approach is 42% of incidents
    • Taxiing is10%
    • Deviation from ATS clearances
      • Assigned flight level 50%
      • RI 21%
    • Contribution to events

Take-Off From A Taxiway Oslo

  • The crew missed the runway 01 L and went from the taxiway M
  • Crew had 3 pilots including trg captain and FO under instruction
  • Runway and taxiway clearly visible from ATC tower
  • Weather day time winter and light haze
  • Take off 1600 meters to take off
  • Lessons
    • Comprehensive pre-departure briefing should eliminate threats
    • Taxi should be seen as critical phase hot spots considered
    • Take off clearance should be done only when ac is on the runway
    • Airport lights and signs to be improved
    • RAAS system installed

Taxiway Landing Ongoing Investigation

  • B767 300ER
  • Landing on taxiway at Atlanta
  • 3 pilots LCA, Captain and FO although LCA was out of the cockpit
  • En route given 27R initially then went to 27L, which they expected
  • Then they were given 27R on approach as a side step
    • The runway lights were not on 20 mins to switch on!
    • Taxiway M was landed on it was open for taxi use with bright led lights on!
    • 10 hours from Rio De Janeiro for both crew
  • Into Seattle, one runway was very bright, whilst the active RW was much darker and they took the brighter closed runway
  • Tie up between stable approach and side step some use 500’. Others use 1000’ gates
    • US airports often go for a side step at 750-500’ on approach

Taxi-Way Take-Off Ams B737

  • B737-3 AMS to WAW
  • Night take-off with light snowfall
  • 2nd flight of the day for the pilots
  • Flt late due to de-icing
  • Took off from a taxiway they did not realise they had done it
  • After de-icing of the ac, the 737 is cleared ahead of another aircraft which was involved in a taxi error at the time, which took ATC attention from the line up on taxi way B
    • The B737 took off the taxiway was not clear of snow at the north end
  • The airline includes costs on its charts map indicating the cost of delays and loss of time incurred when lengthy approaches and deviations are flown
  • Airline Sim Training session recurrence used to be 2 per annum now increased to 3 sessions —-it used to be 4 sessions in the past
  • Crews have now been challenged to discuss flight safety before each flight for 10 mins rather than discuss the mortgage!
  • Captains are encouraged to discuss flight safety concerns en route
  • There have been 2 take-offs and 2 landings on taxiways in past 6 months
  • Runway and taxiway lighting make-up, intensity and colour are all changing due to the introduction of LEDs and need to be considered

Runway Closure

  • Japanese Airport using parallel runways with snow
  • A landing B777 reported runway slippery at the end of the RW via PIREP
  • The next B777 landing was night and the aircraft nose wheel went off the runway at the end due to ice
  • During the incident investigation, the crew was unsure of
    • The SOP for icing landing
    • The use of thrust reverse in skidding situations and the use of idle reverse and no braking until it was too late!
    • The runway lighting is red and white at 2000’ to go
  • The ac landed at 132 kts, was at 57 kts at 3000 ft, but the skid started at 37 kts and ran off the runway surface before stopping

Autoland Runway Incursion LVP Approach

  • B747 landing at Luxembourg thought he saw something on the runway as he touched down
  • The obstacle was a vehicle on the centreline of runway changing the bulbs on the edge
  • LVP ops left a lot to be desired at the airport!
  • Aircraft operator stopped all ops at Lux until a written confirmation of the safety of the airport was issued – took 6 hours
  • Severe vehicle movements in LVPs were introduced at Lux which meant that nothing moved only 3 take-offs per hour maximum for several weeks
  • Criminal investigation of the controllers commenced
  • The tapes were released to the media straightaway
  • Initially, the crew accused of landing without landing clearance
  • An Embraer had received take off clearance and would have hit the van if the crew had not reported their concerns straightway to ATC, who cancelled the E190 take-off

Runway Confusion

  • Shanghai Confusion an A320 on a VOR/DME into RW18
  • The airport had parallel runways under construction
  • The Ac approached the wrong unopened RW so were instructed to go around at 200’ with 900 metres before landing
  • Successful go around achieved
  • Cross checking for the flight crew in CRM training appeared not to work
  • The unopened runway lights were on – this should not happen whilst the runway was still under construction
  • 11 similar events in China in the past 10 years and there have been 8 landings at wrong airport

RUNWAY EXCURSIONS

  • St Kitts Intersection Take off Error
  • 25% de-rate take off from intersection A but they were at intersection B 1220 metres remaining
  • When they call ‘Ready for departure’ ATC asked if they wanted to backtrack by ATC
  • In fact, 988 meters needed to get airborne
  • ATC gave them clearance to go from A and knew that they were at B.
  • The crew missed key taxi and airfield layout information in the pre-brief
  • They taxied thinking that they were at A as they approach B
  • ATC did not say anything!
  • There was an element of distraction due to non-standard use of Flap 20
  • As power comes on, the runway end loomed quickly
  • Corrective action taken as follows by the airline:
    • Debrief crew
    • Talk to local staff
    • Send out an investigator
  • The Airline SOP was that new airfields were not routinely inspected before operational flights commenced, but this has changed.
    • Limited review now in place using experienced crew for inaugural flights with a series of questions to follow up on.
    • Annual reviews of those that have been inspected will now occur.

CRJ 200 BOMBADIER RUNWAY OVER RUN Jan 2010 Charleston West Virginia

  • A successful EMAS encounter(48 EMAS round the world)
  • RTO at high speed
  • 140 meter drop at runway end
  • V1 at 121 kts
  • Flap selected from 8 to 20 degrees whilst travelling down the runway, after a configuration warning
  • Ground spoiler popped out at 140 kts so he RTO’d
  • The ac hit the EMAS at 55 kts
  • Ac out of service for 11 days gear changed and minor scratches

Dual AC Power Loss Q400

  • AC Power was lost due to a harness short on the main spar Q400 through a wiring harness wearing on wire mounting
  • Full maintenance mitigation was undertaken by Bombardier

STEADES ANALYSIS Runway Confusion

  • 50 cases found in the STEADES database of runway confusion

Volcanic Eruption Ash

  • Charts are being produced every 6 hours by WSI and Met Office
  • ICAO says you cannot fly in volcanic ash so airspace closed
  • Therefore London NATS Flow Control closed the IFR
  • Three different ash distribution models have been produced London VAAC, Eurocontrol and WSI
  • London VAAC Met Office chart now taken as the authoritative chart.
  • Past encounters involved 1000 times more concentration than engine manufacturers currently allow
  • Risk assessments and maintenance regime for flying in Europe has been developed by several airlines in conjunction with regulators
    • Engine filters are dropped and inspected nothing found so far
  • The Issues are:
    • What is the risk some ash is normal – 720 gms per hour is the safety margin for B777 Trent engines
    • In black areas, there is less than 0.002 gms of ash
    • Trent takes in 100m3 air per hour
    • Very significant safety margin is currently being applied
    • In excess of 20 non-revenue flights have been undertaken
    • OEM certification progress
      • Airlines are seeking recognition that operators can risk assess the problem and use boroscope and inspection regime to monitor any ash effects

Montserrat Soufriere Hill Eruption The Comparison with Europe

  • 100s of active volcanoes vent around the world
  • Traces of ash is common in the atmosphere and carry minimal risk
  • The current low concentration of ash in European airspace carries:
    • An economical and safety risk
  • In the case of Montserrat
    • Potential ac loss is greater
    • Higher safety risk
    • Higher risk for local airports
  • Although Montserrat is monitored closely, when eruptions occur, the NOTAM warning message sent out is almost impossible to interpret
  • The event can include pyroclastic explosion/flow, which is high threat
    • The NOTAM format is not explicit nor clear about the level of risk
  • Similar events have occurred in Middle East which have gone unnoticed and under-reported generally in the industry

ICAO Activity

  • IATA spoke with ICAO to seek immediate action since this time the eruption impacted high density airspace operations
  • ICAO is now forming an International Volcano Ash Task Force. They will examine:
    • How much ash an engine can take and stay safe
    • How to measure the ash accurately and the area of safety
    • How do you communicate these dynamic changes to pilots and dispatchers
  • Experts will be brought together with NASA, IATA, EASA and meets in June and again in July
  • Other measures will take a year or more to establish

The Eurocontrol Perspective

  • High level teleconference amongst the Eurocontrol executive has identified urgent actions
  • ANSP chiefs brought in to seek actions
  • FABEC States UK CAA and others were brought together for data collection but all are short of resources for analysis
  • Eurocontrol was placed in the lead to draw the info together using EVAIR as the database to be used
  • 1000+reports were received from 23-29 Apr 107 reports with Volcanic Ash detected but no incidents reported as a result
  • 12 Multi-disciplinary teams to deal with VA situation at the operational level
  • Reports are being matched with CFMU info to match flows together
  • Most reports have occurred over the UK
  • No standard taxonomy for VA this is needed
  • Most reports between FL200 and FL290
  • Provisional Council at Eurocontrol meets 5/6 May to discuss the way ahead and to work with ICAO etc
  • Similar eruption event occurred in Iceland which affected Siberia in 2003.
    • ICAO put a team together then but little output resulted.

Diversion On Apr 13 Which May Have A Volcano Connection

  • On the day before Iceland volcano erupted, a CDG to DFW Airbus ac, 2 hours out from Paris over the Atlantic south east of Iceland, 9 cabin crew members only became sick, disorientated and nauseous and diverted into Keflavik Iceland
  • Sulphuric dioxide poisoning around the aircraft thought possible
  • However, Blankets, duvets, food, dangerous goods =all checked out fine
  • Symptoms were sulphur dioxide typical but how about Carbon monoxide which is also emitted by volcanoes

Double Engine Problems

  • Involveda Trent engined A330 en-route Indonesia to HKG with 309 pax 13 crew Both flight crew were experienced
  • Flt time 8 hours
  • Normal TO but in the climb some minor fluctuations on the engine noted
  • Level at FL 390. Left engine 2 control fault indication with ECAM warning
  • Ops dept consulted they instruct to flight to continue and watch for further indications
  • Engine control fault came again – ac told to continue
  • On arrival at the HKG terminal area, RW O7L nominated with some wind shear warnings common
  • During descent through FL230 eng No 1 fault and eng No2 stall warning were indicated at which point a pan was declared and priority landing called
  • 45 miles from HKG at 8000 ft engine No 1 stall warning too – Mayday issued
  • Result was No 2 engine stuck at sub idle No 1 stuck at 70% N1
  • Even with both engine thrust levers closed with above indication
  • Tried Config 1 and kept height to reach airfield
  • Touched down at 230 kts spoilers deployed and thrust reverse did deploy on 1 engine which indicated 79% N1 at stop.
  • 5 tyres blew and hot brakes resulted
  • Smoke and flames reported by the firemen – thus the cabin was evacuated safely minor injuries
  • Pod strike found on the right engine on landing
  • HK CAA are running the investigation
  • Fuel samples taken engine components checked.Suspect fuel contamination to be confirmed
  • Investigation may take 1 year to complete
  • Initial accident report issued at 0800 on 6 May 2010
  • HKG cameras at each end show full evacuation and landing
  • The crew had a serious dilemma on whether to evacuate or not since the communication between rescue and the crew was not clear?

A340 Ground Damage HKG

  • An A340 at HKg (to Zurich)taxied out at night at full load
  • Wheel rim exploded and parts hit No4 engine
  • The ac was at slow taxi speed in a straight line no extra stress
  • Three deflated wheels on the undercarriage
  • Few cockpit indications – fuel flow of engine 4 did twitch
  • Cabin pax saw what happened and had more info than the crew
  • Investigation ongoing
    • Aim is to see where the failure initiated
    • Probably the outer bearing failed followed by the inner bearing under additional load
    • Heating effect caused tyre to exploded
    • Possible torque installation error or wear and particle contamination?
    • Background and history of maintenance and manufacture is under investigation by Airbus

Madrid Airport Task Force – Tony Vander Veldt – Eurocontrol

  • Major increase in traffic at Madrid plan to be No 3 European airport
  • New RWs have been built and complex taxi patterns have resulted
  • Numerous ASRs received taxiways are very confusing, badly marked and badly named
  • The TF has formed to change the taxiway issues
    • Started in Sept 2009 and will end in May 2010
    • New signage being adopted
    • Standard taxi routings are being introduced
    • Design and install vertical signage
  • General taxiway design philosophy
    • There is no standard ICAO RW design philosophy
    • The TF seek to keep Madrid taxi patterns simple
    • Unambiguous: no duplication of taxiway names
  • IFALPA does have a taxiway design philosophy
    • This is being used as the major guidance towards the plan

Eurocontrol EVAIR Scheme

  • The Madrid action plan and the taxiway TF were developed from EVAIR reports
  • 12 areas of concern identified in this plan
    • Redesign of the airspace
    • ATC licensing problem has been resolved Spanish ATC can no longer do all sectors and airfields they need specific certification for each
    • Feedback process is being established between Eurocontrol and the Spanish Authorities (EANA)
    • A workshop is being organised in Nov to raise specific issues with Madrid/Spanish airspace to established quick responses to incidents to aircraft from MADRID including a ‘NATS type’ safety partnership
    • However, the trade unions are very strong and agreements take long negotiations
    • Feedback can only be used for safety and not for prosecutions; hence non-punitive reporting is the issue at this stage.
    • Madrid is the major target for the Action Plan but other airspace issues in Spanish will also be addressed in due course

MADRID Reports Other Inputs

  • ATM/TCAS reports over 1 year at Madrid are by far the highest of any generated in Europe TCAS reports in Palmas are also very high
  • In one major airline, 12 ATM reports per 1000 sectors and 1.4 per 1000 sectors on TCAS are generated at Madrid
  • All airlines are encouraged to report all problems at Madrid in the coming months into EVAIR at Eurocontrol

Ozone Encounter

  • After many years of no reports, a major airline received a major ozone encounter report
  • Crew were short of breathe and confused
  • The recommended action is to wrap wet towels around the nose and mouth
  • Ozone filters/converters are fitted in some but not all aircraft and there is little or no maintenance carried on these filters normally
  • There are implications here for crews and passengers as increasing use is being made of polar routes.

Denial of a Diversion

  • A B747 Cargo ac routing from HKG to AlA needed to divert to a Chinese airfield from its original Kazakhstan airfield due to weather there.
  • The receiving airfield in China refused the diversion
  • It appears there were language misunderstandings between the countries’ involved
  • If All Else Fails Declare An Emergency
  • Eurocontrol have Safety Contact Lists in most countries which airlines can use to obtain feedback when these types of incidents need to investigated.

CRJ 100 ACCIDENT NOV 09

  • 10 paxand 5 crew on the aircraft
  • After take off, the power lever became stuck at 94%
  • The Captain opted to returned to base and landed on second attempt
  • The ac parked and started to unload pax. Suddenly, the ac leapt forward, travelled for 26 seconds from ramp stop and hit the terminal
  • The engine door panel stow rod was stuck against the throttle control since it had not been stowed properly during maintenance
  • The CRJ QRH for a throttle jam is to shut the engine down, but the crew disregarded this action!
  • The high speed landing had affected the brakes, which released on the ramp during the deplaning of the passengers

Rich Jones
Chief Executive
UKFSC

IATA Incident Review – 1 October 2009 – Frankfurt Meeting

IATA Incident Review Meeting DAY 2 1 October 2009Lufthansa Conference Room Frankfurt Airport
CE Meeting Summary

NOTE: CE only attended Day 2 of the Meeting due to ECAST meeting at EASA on Day 1. Main Outcomes from Day 2 were as follows:

Leading Edge Flap Retraction on Take-Off

  • Boeing 747-400 on take off at Jo’burg (hot and high). At 80 knots, the leading edge slats retracted due to symmetrical thrust reverse indications. Aircraft went into heavy buffet at around 80 kts then stick shaker activated at rotate at 128 knots
  • Auto retracted lead slats completed at around rotation stick shaker stopped at 138. At 163kts, the slats then redeployed
    • Auto retract is to save wear on leading slats when reverse thrust I selected during landing or RTO
  • The PH F/O (ex-military pilot) immediately selected TOGA and full throttle at stick shaker and lowered the nose by 1 degree
  • Pilots did not see the thrust reverse indication at the time until after rotate
  • Aircraft was 7 knots away from the stall with 1degree down selected. If 2 degrees down had been selected then ground impact would have occurred
    • If standard pitch been held aircraft would have stalled
  • Aircraft at 95 feet with 50 ft min climb rate by the end of the runway
  • Slats fully redeployed when gnd-air switch closed. The stick shaker re-activated as they did so due to drag
  • Maintenance had used an air cart to check reverse thrust mechanism, which may not push the thrust reverser in as hard as engine pressure does.
  • Crew thought they had thrust reverser issues not stall.
  • Actions to prevent reoccurrence Boeing Safety Board called within 24 hours
    • Revise guidance on maintenance to check thrust reverser fully stowed
    • AD issue to remove thrust stow indicator interlock from the leading edge control now select of thrust reverse is manual via the throttle levers
    • The ‘Stow sensor’ tolerance being reviewed
  • In questions,
    • It was considered that this design failure could not happen now since Risk Assessments are far better now
    • Has automation has gone too far?
    • Is pilot trg sufficient to meet this type of incident?

Supplementary Issues Madrid ATC and airspace

  • Inappropriate ATC responses to TCAS issues and high speeds into approach procedures at Madrid are leading to unstable approaches. These are being pursued by the airline with Madrid directly. Other similar concerns are being sought by IATA through the Marty Maurino.
    • An 200’ airprox incident with a Glider near Madrid was also discussed – gliders were legal and the area promulgated but the crew had not registered the restriction

Significant Indicated Airspeed Anomalies Micro-ice Particles

Air France Accident feedback

  • The Air France A447Interim report is on the website of the BEA but no more evidence has been found
  • Other investigators have been called in and more work is now being done on flight data recorder improvements and on investigating new types
    • Detachable floating recorders used by the military are being looked at since only 10 recorders out of 400 accidents have not been recovered
  • Another option being considered is for Ac data info to be transmitted automatically when certain ac parameters are exceeded

Micro-Particles Events

  • IAS anomalies and ice crystal icing have been hinted at in public recently
  • Data has been collected from ac in areas of high convective activity where IAS has been lost for 20-30 seconds
  • At these times, the data is also showing that the TAT has appeared to increase, significant turbulence but not severe has occurred, rain has appeared on windshield although at -40c.
    • These conditions all point to ice micro crystals being formed – not normal or classic icing -since there is no rain at -40c!¬
  • TAT changes may well be due to the high density ice crystal corruption at the sensor, and the TAT is in fact no higher at all.
  • However, these TAT indicator changes can force engine rollbacks to occur and may be sufficient to cause flame out. (There is at least 1 case of a four- engine flame out over Asia!)
  • The TAT change results from sensor measuring liquid water trapped in the probe and not the air temperature.
  • These crystals are present in or around the ‘green area’ on the Wx radar near the cells but do not show up as red on the radar!
  • A Boeing Ice Particle Threat Paper by Jeanne Mason may be useful to provide more inform on the phenomena
  • These micro-particles have been noted by BA over Bay of Bengal on several occasions during in high convective activity
  • These TAT changes can only be seen from the FD data and are not apparent to the flight crew. Other FDM data mining is being undertaken.

B777 Tail Strikes

  • Report of a B777 taking off from Frankfurt. One hour before the ac departed it was changed from its original gate. Then an MEL item was found in the cockpit which led to further distractions.
  • At the last minute, a cargo change which affected the MTOW was instigated. The flight had 3 captains onboard since it was a check ride.
  • One captain inserted the weight into the EFB but no cross check of FMC was carried out
  • The method to check the TO data card is different for B777 from all other aircraft being operated by the company involved, which resulted in the zero weight being inputted in the FMC instead of the MTOW for the conditions
  • FDM showed a normal pitch rate during rotate was 9.98 degrees. The tail actually hit at 10 degrees but speed calcs for zero wt was 143 for rotate as opposed to 175 (32 knots different)
  • Thrust indicated 92.3% and when it needed 102.7% selected for the weight.

A320 Tail Strike

  • The ac had an unexpected pitch during take off at 50 knots. The crew thought they were in the air due to the high nose-up attitude and continued the take off
  • Both pilots pushed at 113 kts (with full pitch down trim set ) but the pitch increased to + 13degrees pitch up.
  • TOGA selected, the ac actually lifted off at 124 kts with a pitch of +18 and 6 degree roll left once airborne
  • The take off was packs-off. At 4000’ cabin altitude the packs were selected on. The config warning sounded at 10,000 due to frame damage so the ac rtb’d.
  • The cause was probably a loading issue still under investigation
  • Thrust increase via TOGA was wrong selection due to pitch increase!

Similar Callsign Confusion

  • Two examples of serious callsign confusion leading to potential runway incursions cited by Far East Carrier at Osaka Int airport.
    • Callsigns NH18 and NH181 on RW 32L and RW 32R
    • NH503 and NH 513 on RW32L and RW 32R
  • Callsign confusion and callsign co-ordination is being currently addressed by use of callsign deconfliction software at Eurocontrol at airline level and at the European level for States.
  • Eurocontrol to liase with Far East Airline to offer software solution

Engine Rundown A330

  • An A330 on a long haul flight had an engine rundown on approach to a far east airport
  • As a matter of routine, the airline had an SOP to select the recommended fuel feed configuration to address the fuel stby pump pressure low indication which, if left unchecked, would occur on approach to this destination and be a distraction at a critical phase of flight.
  • In this case, the aircraft ended up with gravity feed only Engine No1 failed when increased power was requested on the descent
  • An Icing issue is suspected. This A330 had Trent engines is this another BA777 icing occurrence?
  • Discussion in the forum focused on the difference in actions on selection of the cross-feed between the A320 and the A330. No clear conclusion was reached.

Rich Jones
Chief Executive
UKFSC
14 October 2009

Manchester RSC – 18 February 2009 – Manchester Tower Meeting

Manchester Runway Safety Committee – Manchester Tower- 18th February 2009
CE Meeting Report

Agenda

  • Arisings from the Last Meeting Minutes
    • 8.1 New vehicle entry points designations to introduced using ICAO standards
    • 8.1 New signage for runway protection to be introduced to ensure consistency
      • LVP workshop to be undertaken to analyse individual crossing point risks.
  • ITEM 2
    •  EAPRI review at Eurocontrol is awaited
  • ITEM 3
    •  RUNWAY INCURSION REPORT….draft provide for comment. Final published in due course
      • To be used as a communication tool and to raise general awareness including amongst pilots, drivers and driver trainers
      • Widely circulated amongst all sections at Manchester
    • 3 RI events since the last meeting
      • Technical incursion during LVPs – no runway entry intent – but crossed the protective blue light line into the LSA.
      • Blue light line cross in LVP and into the LSA
      • A dedicated driving training session to be undertaken to remind and retrain all on LVP procedures and R/T – planned for 7 March 2009
      • Blue light line cross during de-icing operations – caused by switch into LVP whilst vehicle was operating beyond the LVP blue light line. Procedure to announce LVP in force to be revised.
  • RI Map is now produced for the RSC which shows hot spots in order to produce  appropriate actions to address the issues – to modify lighting and signage etc
  • ITEM 4 HOTSPOTS
    • FZ1 is the hotspot being addressed due to numbers of incidents in the past.  Much constructive discussion on how to modify the ground approach signage and lighting lay out.
  • ITEM 5 RUNWAY SAFETY AREA
    • Runway surface condition has now been introduced as part of the RSC business
    • Change to Runway overrun area criteria and distances being introduced and agreed with CAA. This exercise has changed the TORA/ASDA/LDA and also standardised the TO distance measurements from each Runway entry point – this has a significant effect on a number of declared distances.
    • Re-texturing of specific runway surfaces particularly for sections of  05L planned in the next few months
  • ITEM 6
    • NATS to introduce a specific Airport Safety Plan at Manchester
    • CE UKFSC provided back brief on RISG and LHR MAST Meetings
  • ITEM 7
    •  RUNWAY SAFETY PLAN
    • 1.   Driver training – competency based system being introduced
      • Current system is robust but useful improvements are to be made – including supervision and nights training
      • R/T competency review on Flt Services Ops drivers/operators plus LVP training being undertaken too – the aim is to pull the elements of driver training together for an integrated training requirement and approach.
    • 2.    Signage, Markings and Ground Lighting Strategy
      • CAPEX review outcomes will change a number of the projects which will need re-prioritising from a safety perspective – for the next meeting
      • Lighting and signage including the RW ahead markings
      • Runway Stopbar Strategy
        • Single Holding Point designator plus simplification of the taxiway designation and nomenclature over the coming summer
      • Work to move to a common Cat Holding positions to be costed.
      • Overall risk analysis ongoing for the changes to be followed by a detailed risk analysis.
      • Long term aim to have a single main parallel taxiway – nominated ALPHA.
      • CAPEX will be the determining factor on success in a big bang change or evolution.
    • 5.     Next phase of Ground Marker trial starts in March 2009
    • 6.     FOCUS article later this year on runway safety
    • 7.     Revised declared distances in May 2009
  • ITEM 8 already covered above at 3.
  • ITEM 9 –
    • Runway Condition Reports
      • Formal runway assessment to be documented each month which covers:
        • Condition
        • Friction assessment
        • Drainage
        • Airfield ground lighting
        • Signage and marking schemes

Rich Jones
Chief Executive
UKFSC

Manchester RSC – 16th August 2011 – Manchester Meeting

Manchester Local Runway Safety Team Meeting – 16 August 11

CE Meeting Summary

Agenda

ITEM 1 – Last Minutes Action Review

  • Runway entry stop bar automatic timer project delayed into Oct 11 to better align with other ongoing lighting and control refurbishments
    • Inclusion of additional audible alarms for stop bar switching in ATC under consideration
  • Review of runway incursion sensor/audible alarm policy to be included as part of the overall runway crossing safety case review.
    • After discussion, decision taken to review the entire runway incursion safety case instead of just the runway crossing review
  • RIMCAS fitted on one runway currently – cost to fit both runways to be investigated
  • ‘Runway Vacated’ sign positioned on one runway exit – policy for wider application of these signs to be reviewed
  • CBT package in development for LVP training for all airside drivers which may be made available to drivers more widely
    • Aim to complete this project for Winter Ops and intro for driver training by Oct
  • Work underway to reduce free ranging driver numbers to absolute minimum

ITEM 3 – Runway Incursion Data Review

Runway Incursions 2010-11 – (Rolling Year).

  • Four incursions since last meeting – three pilot and one ATC/pilot shared
  • Discussion about permission for fire crash services to cross a red stop bar in an emergency.
  • Emphasise the need to get clearance and not assume it!
  • UKFSC Brief on FAA and PubRel summary on landing without clearance incidents
  • New single hold policy – may lead to pilot expectation of another hold further on, hence increase in the risk of crossing a stopbar (1 such event so far at Manchester):
    • 6 Aug 11 incident occurred with old hold markings still in place – these need complete paint out
  • Other RI prevention measures considered:
    • Add hotspot to next AIRAC
    • Runway designator signs to be painted at all entrances (for consistency)
  • UKFSC briefed on possible misunderstanding between ATC and airport operator on light sequences and operation
  • Decision to reflect need to check lighting operations in ops manuals

ITEM 4 – UK National Meeting Activity 

  • Feedback on related national activity provided by UKFSC

ITEM 5 – Review against EAPPRI 2

  • To be reviewed in detail against all aspects
  • CAA Questionnaire can be expected on EAPPRI2 activity

ITEM 6 – Runway Safety Plan Review

  • Driver training to be reviewed in light of new CAA CAP 790
  • Phase 1 of stop bar improvement programme underway
  • Phase 2, including removal of Cat 1 hold positions, now subject to Capital Plan
  • Protection of runway and LSA at vehicle access points – signs and markings to be upgraded
  • Communications and Runway Incursion technology to be reviewed in light of EAPPRI 2.
  • Runway Incursion prevention publicity to be developed for pilots and drivers after completion of a causal factors analysis.
  • Grass burn line plan to delineate with signage change

ITEM 7 – Runway Condition Reporting

  • Review new requirements for runway friction status measurement and reporting after Winter 11/12

ITEM 8 – AOB

  • UKFSC mentioned complexity of Manchester taxiways which had attracted some concern from pilots unfamiliar with Manchester.
    • Numerous legacy infrastructure issues and considerable airport development had caused this – once capital programme is complete – possibility of reviewing the taxi markings and layout

Rich Jones
Chief Exec
UKFSC
30 Aug 2011

Manchester RSC – 16 February 2010 – Manchester Meeting

Manchester Runway Safety Committee Meeting – 16 February 2010
CE Meeting Summary


Agenda

Item 1 – Actions from last Minutes

  • 2.2 Vehicle runway entry signs will be in place in next month or so.
  • 2.4 Runway stopbars to be fitted with automatic timers to switch back to red. These were fitted at Birmingham successfully although some work will be required from the ATC to select most effective switching routine.
    • ATC to start monitoring the timing for the each crossing to identify the best methodology and timing for the auto timers.
    • Flight deck consultation was recommended to check for any pilot actions at stopbar which may affect auto timer settings.
    • Stop bar is timer activated only – microwave detectors are a warning only of a stopbar crosser.
  • 2.7 Grass cutting procedure is completed – including controls and radio frequencies. The policy is that cutting within the runway cleared and graded area (extends to 105m from runway centreline) is done at night and in good visibility conditions. A re-brief all grass cutting personnel involved to be undertaken.
  • 2.8 A periodic review of the Runway Incursion Safety Case is underway
  • 2.9 A reminder is to be sent to ATC that runway FOD needs to be treated seriously. (Concorde accident connection!)

Item 2 – Regulatory Standards

  • Specific Drivers may need an update on red stopbar crossing and a team brief and the latest SI will be made available to them.  CAP 493 Supplement attached.
  • Next EAPRI (Runway Incursion Initiative) draft will be out in spring.

Item 3 – Runway Incursion incident Data

  • RI Data
  • Comparison with other airports on counter RI work shows a sound improvement.

Item 4 – Hotspots

  • A number of incidents around JA/1/2 and JS1 at the RW 23R end have been identified and a major work is being scheduled to address the problem
  • The Runway incident at Luxembourg where a vehicle on the runway was hit by the main undercarriage of an approaching B747 was discussed at length to ensure no repeat possible at Manchester. Incident to be advertised widely among the transport driver community who use the airfield.
  • The potential misunderstanding that ‘No ATC Clearance to land’ does not mean an approaching aircraft will not land or roll. Situational awareness statements should be included in the ATC comms whenever landing clearance is withheld.

Item 5 – National Forum Feedback

  • CAA RE TF (Already reported on the UKFSC website under External Meeting Summaries)
  • BALPA Meeting on runway friction reporting on 23 Feb 10.
  • NATS SPA feedback on NATS runway incursion initiative
  • Heathrow MAST feedback (already reported on UKFSC website)
  • Discussion on landing criteria with a tailwind.
  • It was noted that Airbus requires TODA in metres and Boeing want it in feet – this will need to be displayed carefully on signage on the airfield.

Item 6 and 7 – Review of Runway Safety Plan including Stop bar changes

  • Runway Safety Plan
  • Juliet/JS/JA area is being configured for a single taxi path and taxi block off which will cost £500k – final approval is close to sign off. Work to be complete in July 2010.
  • Northside RW entry/crossing points to be reconfigured to have a single hold for all CATS, to reinforce the runway incursion measures already in place.
  • Overall plan is to make the manoeuvre area routings much more simple and safer.
  • Holding point re-designation will be required due to stopbar and holding point works. Re-designation will be based on the hold nearest the RW entry will always be No1 and the remainder re-sequenced back to the ramp area.
  • The new CAA Driver Standards and Training  CAP has been circulated for airport operator comment and will go for formal consultation in March.
  • Installation of more VHF radios in vehicles commences next month
  • GPS tool for runway proximity warning for vehicles using the runway regularly being investigated and fitting is imminent.
    • NATS are also looking at GPS tools applications in the round.

Item 8 – Runway Condition Reports

  • New runway surface is working well – although higher rubber deposits from tyres will therefore need more cleaning.
  • A formal assessment of rubber contamination has been developed and issued.

Item 10 – AOB

  • The method of providing airline users with timely information on Work In Progress around the airfield was discussed. The emailed Map method used by Gatwick was suggested as one possible solution.

Rich Jones
UK Flight Safety Committee
18 February 2010

Met Office User Forum – 4 August 2010 – CAA Kingsway Meeting

Met Office User Forum Meeting – 4 August  2010 – CAA Kingsway

CE Meeting Summary

Agenda

ITEM 2. – Review of Actions since last meeting

  • BAA to brief the Met Office on the CROPS (reduced wake turbulence separation) trial at Frankfurt.
  • The Met Office has met the IATA requirement to cap met costs.
  • Work ongoing on the Probabilistic forecasting of severe (FOG/Snow/Wind) weather out to 15 days for Heathrow, in order enable resilience planning.
  • Medium level significant weather for FL100 to FL450 to be made more readily available to airlines on request.
    • Will also appear the new website in due course
  • Auto-metars. Work on the instrumentation requirements for auto-metar observation platforms at airports to meet the desired weather outputs ongoing in concert with ICAO
  • Spain is now issuing 24 hour metars which is proving useful to easyJet .

ITEM 3 – Review of Costs for Met 2010 – 2012

  • Next year Met costs are based on the current year fees plus AEI inflator of 2.8% on identical service outputs
    • This includes an annual efficiency for services and 1.25% saving at core
    • R and D prog of £217K
    • Additional NATS service costs
  • Volcanic ash costs incurred this year so far is £834K
    • Plus further VA development work costs expected in 2011 of £570K, which includes sat usage enhancement costs
    • Plus Contingency ac costs of £760K Capital plus £0.7-£1M operational costs (volcano sampling)
  • Total met cost for aviation for 09/10 – £27.5M. For 10/11. – £27.9M. For 11/12 – £28.2M
  • The Forum debated the fairness of UK airlines picking up the entire cost of the VA work by the Met Office and the view was that other international airlines and Government should also share in the burden of these costs!
  • The final decision on who pays for volcanic ash costs have yet to be agreed by the CAA, Government with the Met Office
  • The Forum went on to discuss the potential efficiencies that could be accrued by forming a single met provider globally or regionally, since this would reduce met service costs to airlines.
  • In response to airline concerns with Met Service costs, Director CAA DAP declared himself open to any ideas and proposals on costs and invited inputs from UK Met Users.

ITEM 4 – 2011-12 R & D Proposals

  • New proposals on R & D subjects are always welcomed by the Met Office
  • R&D Proposals for 2011 are as follows:
    • Terminal area wind nowcasting
      • A Swedish method is already in place.
    • LVP forecasting
      • Hi-res forecasting and result demonstrations
    • Doppler radar 3D winds
    • Icing/Turb/Cb forecasting
      • Developing mod/severe conditions forecasts and visual products

ITEM 5 – Review of Volcanic Eruption

  • VAAC and Dispersion Modelling
    • 9 VAACs in the world – 2 more likely in Russia an Chile
    • ICAO (Annex3) provides VA guidance and expert back-up
    • In 2006, as aresult of the eruption of Grimsvotn in the EUR region (Iceland) a contingency plan for VA was generated at the Met Office
    • 6 monthly VA exercises held across Europe monitored by ICAO
  • Roles of VAAC
    • VAACs should publish when any ash is present in the atmosphere London VAAC uses 2×10-4g/m3 as the switch over point.
    • VAAC advisories and graphic forecasts are produced out to 24 hours for UK Met Watch Office
    • CAA regulates London VAAC for ICAO
    • Met Office is now producing numerous VA related products
      • For example VA Charts every 3 hours covering 5000’ layers
  • Engine Manufacturers have been asked many times over the past years to provide safe ash levels but had failed until this last crisis
  • Dispersion Modelling
    • Wind, rainfall and temperature are the key factors in the model
    • The London NAME model is the most accurate model available globally
    • Washington VAAC model does not use VA wash-out, hence it is less accurate
    • The London NAME model has been tested on Gulf Oil fires, Buncefield and Chernorbyl and proven to be exceptionally accurate.
    • The major unknown factors are the actual content of the volcano ash release and effective height of plume.

ITEM 6 UK Met Office/CAA VA No Fly Zone Visualisation Tools – Logan air input

  • Airline Ops Departments expressed concern about the lack of availability of any form of visualisation for NOTAM data for VA
  • Some airlines used Jeppeson elink to place lat and long points on the map then used a Microsoft office package to join the dots
  • NOTAM/VA plotting by humans and using all sorts of software was subject to human error – and these did occur
  • After discussion in the Forum, it was clear that no airlines had best practice

ITEM 7 – High Level Ice microparticles/wake vortex/airborne met info via ACARS/ runway surface friction and airport co-ordination – UKFSC Input

  • High level ice micro-particle predictions – is the Met Office able to identify when these may be present.
  • Wake vortex prediction – its increasing importance in SESAR and NextGen
  • Use of Aircraft info for dynamic weather forecasting – severe weather ACARS
  • Runway friction measurement and reporting
    • Using systems to predict contamination build rates to provide better co-ordination of airport closures in poor weather – winter operations
  • The possibility of these being included under R&D projects was suggested.

ITEM 8 – Forecast QNH/Altimeter Setting Region System – BALPA Rep Proposal

  • Currently there is much effort invested by the Met Office into producing Regional Pressure Settings
  • No other countries use the RPS and it is not ICAO compliant
  • BALPA proposal is to drop the RPS scheme all together and for UK aviation to adopt the use of the nearest airfield QNH
    • This will be reviewed by the Met Office this coming year.

Rich Jones
Chief Exec
UK Flight Safety Committee
6 August 2010

Loading...