Preventable / Predictable
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Preventable / Predictable
You may (or not) have seen the current 'Inevitable new bike thread'.
It raises the point of whether crashes are either preventable or predictable. The two are not the same.
And with predictable, let's look at a fairly random event:
Probably not something you would worry too much about. Can't happen that often, can it?
It raises the point of whether crashes are either preventable or predictable. The two are not the same.
And with predictable, let's look at a fairly random event:
Probably not something you would worry too much about. Can't happen that often, can it?
Even bland can be a type of character
- Cousin Jack
- Posts: 4465
- Joined: Mon Mar 16, 2020 4:36 pm
- Location: Down in the Duchy
- Has thanked: 2554 times
- Been thanked: 2287 times
Re: Preventable / Predictable
Neither is predictable in the everyday sense of the word. Both are predictable in the sense that a single point of failure exists (the tow ball) and when and if it fails something untoward and potentially life-threatening will happen. The usefulness of that prediction is not high, knowing that any caravan you meet on the road has a 0.0000000000000001% chance of detaching when you are nearby is unlikely to alter your driving.
Both are preventable with a fail-safe cable/chain secondary attachment.
Both are preventable with a fail-safe cable/chain secondary attachment.
Cornish Tart #1
Remember An Gof!
Remember An Gof!
-
- Posts: 13957
- Joined: Mon Mar 16, 2020 7:57 pm
- Location: Milton Keynes
- Has thanked: 2552 times
- Been thanked: 6257 times
Re: Preventable / Predictable
I don't think you need to predict the specific set of circumstances to anticipate that something might come in to your lane. It's just as likely (more likely probably!) that someone has a heart attack at the wheel and swerves onto your side, or sneezes, or avoids a dog that runs out into the road etc.
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
Yup, a good summary, although I don't know how accurate your 0.0000000000000001% estimate is.Cousin Jack wrote: ↑Sat Jun 05, 2021 2:42 pm Neither is predictable in the everyday sense of the word. Both are predictable in the sense that a single point of failure exists (the tow ball) and when and if it fails something untoward and potentially life-threatening will happen. The usefulness of that prediction is not high, knowing that any caravan you meet on the road has a 0.0000000000000001% chance of detaching when you are nearby is unlikely to alter your driving.
Both are preventable with a fail-safe cable/chain secondary attachment.
But, just for fun: how many caravans have you seen invading Cornwall each year, and how many years have you lived there?
This cumulative aspect was covered IIRC in Top Gear's African trip, about not sleeping under trees in case a branch fell off (one did). Rare event. But if you live to 70 and have slept under a tree for ever night, that increases the likelihood of it happening.
As for caravans, etc., I've seen a trailer escape from a truck (it went from lane 1 to the central reservation, between the car I was in and the one in front), but it's not something that I would be overly concerned about. It's probably far more likely to encounter a motorcyclist going for an overtake.
However, the point is two-fold.
- Preventable and predictable are two very different things
- If we know the types of crash scenario that are common, we can prepare for them
Even bland can be a type of character
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
One that surprised me when I hesrd about it is that it's apparently 'common' for the winch cable on recovery trucks to fail, the go from the inside, so not easy to identify until 'twang'. (I've seen one of those, too)Cousin Jack wrote: ↑Sat Jun 05, 2021 2:42 pm Both are preventable with a fail-safe cable/chain secondary attachment.
The safeguard is similar to fall arrest systems, but they're not used by everyone.
Even bland can be a type of character
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
I'm in a cheerful mood today
Had one of those. Big hgv sized horsebox oncoming, overcooked a bend, then back to the correct lane. Between two of a string of bikes on an advanced course. I was at the back, towards the crest of a hill, had a grandstand view.
Even bland can be a type of character
-
- Posts: 13957
- Joined: Mon Mar 16, 2020 7:57 pm
- Location: Milton Keynes
- Has thanked: 2552 times
- Been thanked: 6257 times
Re: Preventable / Predictable
A guy I used to work with was in an accident that totalled his car, the other guy had a heart attack and drifted over the line at speed.
My colleague was hurt fairly badly but made a full recovery. 'Fortunately' they reckon the other guy was already dead before the accident happened...I don't fancy being in cardiac arrest AND a car accident.
I've been hit by a falling branch when driving (in the car luckily). Surprised the hell out of me that one! I do admit to giving over hanging trees more of a look these days
My colleague was hurt fairly badly but made a full recovery. 'Fortunately' they reckon the other guy was already dead before the accident happened...I don't fancy being in cardiac arrest AND a car accident.
I've been hit by a falling branch when driving (in the car luckily). Surprised the hell out of me that one! I do admit to giving over hanging trees more of a look these days
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
After a fatality, years ago, on the M3, I'm always wary of anyone on bridges.Mr. Dazzle wrote: ↑Sat Jun 05, 2021 4:46 pm I do admit to giving over hanging trees more of a look these days
Even bland can be a type of character
-
- Posts: 3189
- Joined: Mon Mar 16, 2020 3:45 pm
- Location: RoI
- Has thanked: 1264 times
- Been thanked: 1188 times
Re: Preventable / Predictable
'Common' but vanishingly rare. I may be paraphrasing Spin.
I've taken to watching Aussie dashcam footage on YouTube - it has accelerated the learning process and my screen scan has become more predictive / accurate
whether or not that translates to the road remains to be seen. (sic)
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
Or, not as common as some might have us believe?
However - and, as I'm sure you realised - common as in biggest chunk of the stats.
Filly gave me a lift to work one morning (in her bright red car). Someone drove out in front at a mini roundabout. She reacted appropriately then, perhaps inappropriately, in a vocal manner. I just sat there. She asked something like "Doesn't that annoy you?" I replied that, on a bike, it's something that happens just about every day, it's not a surprise, you just deal with it.
Even bland can be a type of character
- Noggin
- Posts: 8031
- Joined: Thu Mar 19, 2020 1:46 pm
- Location: Ski Resort
- Has thanked: 16228 times
- Been thanked: 3929 times
Re: Preventable / Predictable
A family member was driving a car that was the third to go over a jumper on the M5 . Like you say - always wary of people on bridges even though I wasn't thereHorse wrote: ↑Sat Jun 05, 2021 5:14 pmAfter a fatality, years ago, on the M3, I'm always wary of anyone on bridges.Mr. Dazzle wrote: ↑Sat Jun 05, 2021 4:46 pm I do admit to giving over hanging trees more of a look these days
Life is for living. Buy the shoes. Eat the cake. Ride the bikes. Just, ride the bikes!!
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
The guy on the M3 collected a chunk of concrete dropped from a footbridge. There have been other but, luckily, rare, events.
A few years ago, I was riding under a footbridge, with youths up there. A glance up showed that one was on the outside of the rail
A few years ago, I was riding under a footbridge, with youths up there. A glance up showed that one was on the outside of the rail
Even bland can be a type of character
- Dodgy69
- Posts: 5463
- Joined: Mon Mar 16, 2020 6:36 pm
- Location: Shrewsbury
- Has thanked: 1750 times
- Been thanked: 2085 times
Re: Preventable / Predictable
How many folks put the breakaway cable around the tow ball. Not good if tow ball let's go, it happens.Cousin Jack wrote: ↑Sat Jun 05, 2021 2:42 pm Neither is predictable in the everyday sense of the word. Both are predictable in the sense that a single point of failure exists (the tow ball) and when and if it fails something untoward and potentially life-threatening will happen. The usefulness of that prediction is not high, knowing that any caravan you meet on the road has a 0.0000000000000001% chance of detaching when you are nearby is unlikely to alter your driving.
Both are preventable with a fail-safe cable/chain secondary attachment.
Yamaha rocket 3
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
And that reflects one of the things that Spin said recently, it's not just what could go wrong but the consequences if it does.Dodgy knees wrote: ↑Sat Jun 05, 2021 9:10 pm How many folks put the breakaway cable around the tow ball. Not good if tow ball let's go, it happens.
I mentioned in the other thread how US training was years (a decade) ahead of UK Roadcraft. One area was 'risk' and risk management.
And, if you ever do this sort of thing, a risk assessment looks at factors including how likely it is to happen and how serious the consequences are.
But ... is it that users don't know how to use the breakaway cable, or are not aware that the ball might let go, or .... ?
The solution might be to make the optimum fitment a 'default by design' ie the easiest place is the best place. And have a cable that is not an option, it's there, so owners are more likely to use them.
As an example, when I was using a VFR800, my disc lock fitted neatly onto a pillion footrest hanger, so it needed just a few moments to transfer onto the front wheel. But when stored in a BMW pannier it would be slightly more awkward and time consuming.
So, to use an industry expression: engineer out the opportunity to fail*
* I might have misquoted that, or even invented it
Even bland can be a type of character
- Cousin Jack
- Posts: 4465
- Joined: Mon Mar 16, 2020 4:36 pm
- Location: Down in the Duchy
- Has thanked: 2554 times
- Been thanked: 2287 times
Re: Preventable / Predictable
First rule of network security - always look for the single point of failure. A surprising number of network 'security' systems rely on a common power supply, or route via a common node.Dodgy knees wrote: ↑Sat Jun 05, 2021 9:10 pm How many folks put the breakaway cable around the tow ball. Not good if tow ball let's go, it happens.
Cornish Tart #1
Remember An Gof!
Remember An Gof!
-
- Posts: 4096
- Joined: Mon Mar 16, 2020 6:17 pm
- Has thanked: 2636 times
- Been thanked: 1523 times
Re: Preventable / Predictable
Impressed with the speed the guy in the first vid gets his hazards on... it usually takes me about five minutes to remember which vehicle I'm driving and where the button is
"If a man does not keep pace with his companions, perhaps it is because he hears a different drummer." Henry David Thoreau
www.ko-fi.com/survivalskills www.survivalskillsridertraining.co.uk www.facebook.com/survivalskills
www.ko-fi.com/survivalskills www.survivalskillsridertraining.co.uk www.facebook.com/survivalskills
-
- Posts: 4096
- Joined: Mon Mar 16, 2020 6:17 pm
- Has thanked: 2636 times
- Been thanked: 1523 times
Re: Preventable / Predictable
As a general rule, what's predictable is likely to be preventable. I tore an ankle ligament a few years back running up stairs two at a time. Predictable? Yes, Preventable? Yes, don't run up stairs, particularly a steeper-than-usual set.
But you also have to look at 'chance of something going wrong'. I'd been running up stairs for decades, I'd tripped occasionally but never landed badly enough to do any serious damage.
The 'single point of failure' that CJ introduces is interesting - and gives us an interesting way of thinking about the stress points in a system to see where it'll break.
When we're talking about some bike crashes, we can find these points of failure in any particular manoeuvre fairly easily - for example, on a non-ABS bike with a rider performing an emergency stop the point of failure is braking so hard that a tyre starts sliding - and the really dangerous one is locking the front wheel. And similarly, being side-swiped on a motorway is usually directly related to sitting in the driver's blind spot.
Other crashes are more complex with multiple points of failure - the cornering 'clusterfuck' is a good one - in too fast, turn in too early, hit the apex off line, run wide on the exit.
But once we can see the point(s) of failure for ourselves, then we can usually come up with a strategy to prevent the error:
- practice firm braking and don't brake so sharply
- note where you are with respect to other vehicles and don't sit in blind spots and certainly don't sit alongside vehicles for prolonged periods on multilane roads
- if in doubt, default to the brakes so you don't enter quite so fast, then use the Survival Skills system of 'Reference Points' to time machine inputs to the shape of a corner
And there may also be strategies to correct the error - use a security chain with the tow ball in the caravan examples!
- if the front locks, release the brake then reapply a little more gently
- if you realise the driver can't see you and is moving into your space, use the horn and get out from there
- if you're too hot into a bend, use the brakes into the first part of the corner; if you turn in too early and get off line, sit the bike up then lean over again; if you're running wide on the exit, apply some extra counter-steering input and make a quick correction before you run off road
But although that makes a failure more predictable in purely mechanical terms if you're looking for, it doesn't necessarily mean that it'll happen frequently. We need to understand the likelihood of making an error, or encountering someone else's, or even experiencing a predictable mechanical failure. We know the stats, we know what the likely crashes are - SMIDSYs, cornering crashes, overtakes that go wrong are the three main ones crashes - but a surprising number of riders run out of fuel (which can be tricky if you're on a motorway with no hard shoulder - so use the fuel gauge, the trip meter if you don't have a fuel gauge and factor in a safety margin of 25% to compensate for higher fuel consumption into headwinds and bigger gaps between services than you expect) and of course, bikes also get totally unpredictable punctures (don't ride over areas covered in crap, don't use trackday tyres on the road, don't run your tyre to the last mm of tread).
But here's another interesting change-of-perspective. SMIDSY's are an everyday occurrence - at least, they are from the rider's perspective...
...BUT and it's a huge but... they are NOT an everyday occurrence for the driver. Since there are far fewer bikes AND we don't travel so far, we're outnumbered about 100 to 1 on the roads.
And that means the driver about to create the SMIDSY for the rider has far less experience of making the mistake than the rider has of being on on the receiving end.
And this is why I bang on so much about why we shouldn't be expecting the driver to anticipate and correct the error at his end, and why the rider should actually be learning not to ride into it!
But hey, when did logic matter when you can play the good old blame game?
But you also have to look at 'chance of something going wrong'. I'd been running up stairs for decades, I'd tripped occasionally but never landed badly enough to do any serious damage.
The 'single point of failure' that CJ introduces is interesting - and gives us an interesting way of thinking about the stress points in a system to see where it'll break.
When we're talking about some bike crashes, we can find these points of failure in any particular manoeuvre fairly easily - for example, on a non-ABS bike with a rider performing an emergency stop the point of failure is braking so hard that a tyre starts sliding - and the really dangerous one is locking the front wheel. And similarly, being side-swiped on a motorway is usually directly related to sitting in the driver's blind spot.
Other crashes are more complex with multiple points of failure - the cornering 'clusterfuck' is a good one - in too fast, turn in too early, hit the apex off line, run wide on the exit.
But once we can see the point(s) of failure for ourselves, then we can usually come up with a strategy to prevent the error:
- practice firm braking and don't brake so sharply
- note where you are with respect to other vehicles and don't sit in blind spots and certainly don't sit alongside vehicles for prolonged periods on multilane roads
- if in doubt, default to the brakes so you don't enter quite so fast, then use the Survival Skills system of 'Reference Points' to time machine inputs to the shape of a corner
And there may also be strategies to correct the error - use a security chain with the tow ball in the caravan examples!
- if the front locks, release the brake then reapply a little more gently
- if you realise the driver can't see you and is moving into your space, use the horn and get out from there
- if you're too hot into a bend, use the brakes into the first part of the corner; if you turn in too early and get off line, sit the bike up then lean over again; if you're running wide on the exit, apply some extra counter-steering input and make a quick correction before you run off road
But although that makes a failure more predictable in purely mechanical terms if you're looking for, it doesn't necessarily mean that it'll happen frequently. We need to understand the likelihood of making an error, or encountering someone else's, or even experiencing a predictable mechanical failure. We know the stats, we know what the likely crashes are - SMIDSYs, cornering crashes, overtakes that go wrong are the three main ones crashes - but a surprising number of riders run out of fuel (which can be tricky if you're on a motorway with no hard shoulder - so use the fuel gauge, the trip meter if you don't have a fuel gauge and factor in a safety margin of 25% to compensate for higher fuel consumption into headwinds and bigger gaps between services than you expect) and of course, bikes also get totally unpredictable punctures (don't ride over areas covered in crap, don't use trackday tyres on the road, don't run your tyre to the last mm of tread).
But here's another interesting change-of-perspective. SMIDSY's are an everyday occurrence - at least, they are from the rider's perspective...
...BUT and it's a huge but... they are NOT an everyday occurrence for the driver. Since there are far fewer bikes AND we don't travel so far, we're outnumbered about 100 to 1 on the roads.
And that means the driver about to create the SMIDSY for the rider has far less experience of making the mistake than the rider has of being on on the receiving end.
And this is why I bang on so much about why we shouldn't be expecting the driver to anticipate and correct the error at his end, and why the rider should actually be learning not to ride into it!
But hey, when did logic matter when you can play the good old blame game?
"If a man does not keep pace with his companions, perhaps it is because he hears a different drummer." Henry David Thoreau
www.ko-fi.com/survivalskills www.survivalskillsridertraining.co.uk www.facebook.com/survivalskills
www.ko-fi.com/survivalskills www.survivalskillsridertraining.co.uk www.facebook.com/survivalskills
Re: Preventable / Predictable
It's because you're older than you were.... I definitely note a reduction in flexibility and agility (not that I ever had much of either). Wait till you're in your 80th decade.......The Spin Doctor wrote: ↑Mon Jun 07, 2021 8:47 am As a general rule, what's predictable is likely to be preventable. I tore an ankle ligament a few years back running up stairs two at a time. Predictable? Yes, Preventable? Yes, don't run up stairs, particularly a steeper-than-usual set.
-
- Posts: 4096
- Joined: Mon Mar 16, 2020 6:17 pm
- Has thanked: 2636 times
- Been thanked: 1523 times
Re: Preventable / Predictable
Sadly, there's some of that in it... I used to manage them three at a time... in full bike kit when I was a courier!! I always made a point of running up any set of stairs up to three flights. I hadn't realised just how fit that had made me until I was in the Alps at 6000 ft and the lifts failed in our apartment block... and I RAN up to the 7th floor! When I got home, I weighed my riding kit - which included full leathers - nearly two stone! That explained itiansoady wrote: ↑Mon Jun 07, 2021 10:15 amIt's because you're older than you were.... I definitely note a reduction in flexibility and agility (not that I ever had much of either). Wait till you're in your 80th decade.......The Spin Doctor wrote: ↑Mon Jun 07, 2021 8:47 am As a general rule, what's predictable is likely to be preventable. I tore an ankle ligament a few years back running up stairs two at a time. Predictable? Yes, Preventable? Yes, don't run up stairs, particularly a steeper-than-usual set.
Unfortunately I'm badly out of practice now... ground floor flat
"If a man does not keep pace with his companions, perhaps it is because he hears a different drummer." Henry David Thoreau
www.ko-fi.com/survivalskills www.survivalskillsridertraining.co.uk www.facebook.com/survivalskills
www.ko-fi.com/survivalskills www.survivalskillsridertraining.co.uk www.facebook.com/survivalskills
- Horse
- Posts: 11560
- Joined: Sun Mar 15, 2020 11:30 am
- Location: Always sunny southern England
- Has thanked: 6198 times
- Been thanked: 5088 times
Re: Preventable / Predictable
Remember the 'Miracle on the Hudson'? This popped up on LinkedIn (linked article includes videos and illustrations. It's a bit tldr.
http://aerossurance.com/safety-manageme ... foresight/
Power of Prediction: Foresight and Flocking Birds
On 15 January 2009, two minutes after take off from LaGuardia Airport (LGA), New York City, US Airways Flight 1549, Airbus A320-214, N106US, encountered a flock of Canada Geese. The US National Transportation Safety Board (NTSB) investigation report says:
Both engines were operating normally until they each ingested at least two large birds (weighing about 8 pounds each), one of which was ingested into each engine core, causing mechanical damage that prevented the engines from being able to provide sufficient thrust to sustain flight.
Consequently the aircraft was forced to ditch in the Hudson River. The 155 passengers and crew members successfully evacuated the aircraft and were rescued with only 5 serious injuries.
The executive summary of the NTSB report covers many aspects of Crew Resource Management (CRM), training, ditching procedures / certification and survivability related to actions after a bird strike that prevent continued safe flight.
The NTSB summary only briefly mentions mention engine certification standards and wildlife hazard mitigations to prevent critical damage.
In this article we look at how hindsight from previous occurrences demonstrated the potential of such an accident and how prediction had shown the probability of a catastrophic bird strike outside the airport boundary was increasing.
Canada Geese: the Large Flocking Bird Hazard
Canada Geese (Branta canadensis), as a species are a major threat to aviation safety for there reasons:
Their large size (at an average of c8lbs+) means that a Canada Goose strike is at the top end of certification requirements for large aircraft
Their propensity to fly in ‘skeins’ (v-shaped flocks) which mean that multiple simultaneous strikes are possible
While traditionally a migratory bird, they have increasingly become non-migratory
Its this third factor that had been causing the risk of a double engine bird strike to increase. The NTSB published a chart of US Canada Goose population, which had increased from 1.2 million to 5.5 million over 38 years:
The nearly 20 fold increase in resident geese is significant as that means even greater exposure throughout the year.
This change in behaviour had come about because Canada Geese had increasingly been adapting to live year round in parks, golf courses and waterways in an around urban environments, while still flying in skeins to local feeding areas.
Readers of the NTSB report might conclude that this was something of a surprise to the industry.
Foresight not Hindsight and the Environmental Aspects of Bird Hazard Mitigation: Warning of Probabilities
In fact, among others, the UK Civil Aviation Authority (CAA) had been paying close attention to the threat of large flocking birds and the probability of a catastrophic a multi-engine bird strike. In a paper authored by Aerossurance’s Andy Evans, then a UK CAA Surveyor, the UK CAA warned that:
In some areas of North America, the risk of such an encounter may be approaching a critical level.
This was 8 years before A320 N106US lost power from both engines and ditched in the Hudson River.
At that time rule making to enhance engine bird strike resistance for new engines was already under way.
As there was little that could be done to enhance existing designs this paper was intended to highlight the critical need to take proactive environmental action to manage bird habitats.
While this included measures on and close to airports it also crucially included wider actions involving non-aviation stakeholders, the UK CAA paper endorsing a set of recommendations from the Aerospace Industry Association (AIA).
Although the Flight 1549 bird strike occurred beyond the range of the airport’s wildlife hazard responsibilities, the NTSB’s only environmental safety recommendation (A-10-75) after the Hudson ditching was focused on airports. This recommendation was directed to the Federal Aviation Administration (FAA) to ensure all US Part 139 US airports had conducted a Wildlife Hazard Assessment (WHA) and implement, if needed, a Wildlife Hazard Management Plan (WHMP). Completely contrary to the basic concept of a Safety Management System (SMS) and risk management principles a WHA is still today only required after a ‘triggering event’ according to 14 CFR 139.337 and this recommendation remains classified as open by NTSB.
One press report states that the Port Authority of New York and New Jersey (PANYNJ) has killed 70,000 birds between 2009 and October 2016. Just 1,830 were Canada Geese, with the majority much smaller birds. The really powerful risk mitigations remain those to manage bird habitats in urban areas.
Meanwhile Aerossurance is aware that, we think bizarrely, the concept of ‘Prediction’ is actually going to be removed from the next revision of the ICAO Safety Management Manual to leave just ‘Reactive’ and ‘Proactive’ approaches. Having three categories is allegedly seen as “too confusing” apparently. We think that’s a retrograde step.
But Not Forgetting Hindsight: Warning of Consequences
Some readers might be sceptical that even though it was being discussed around a decade before the Hudson River ditching, the aviation industry and wider stakeholders could really be expected to see the significance of the rise in the Canada Goose population before a major accident (in the same way that WHA’s are only required after the first ‘triggering event’ at an airport).
However there had been noticeable accidents and serious incidents involving geese in the late 1990s, listed in the UK CAA paper, that had been sufficient to trigger engine certification rule making:
June 1995 an Air France Concorde struck Canada Geese while landing at John F. Kennedy International Airport. Two of the four engines caught fire and were destroyed. Air France sued the airport operator. The case was settled trial for a reported USD$5.3 million.
September 1995 a US Air Force (USAF) Boeing E-3B crashed on take off in Alaska killing all 24 on board. The investigation concluded that the probable cause was the ingestion of Canada Geese into number 1 and 2 engines after they had been disturbed by a previous aircraft’s take off.
January 1998 a Delta Boeing 727-200 made a safe landing in Houston, TX after all three engines were extensively damaged, as were the leading edge slats, radome and airspeed pitot tube after striking geese at 6000ft in the climb
September 1998 a United Boeing 767-300 struck a flock of geese just prior to touchdown at London Heathrow. This caused extensive to the left hand side of the aircraft. This occurrence lead to a number of AAIB safety recommendations.
November 1998 a British Airways Boeing 747-100 encountered a flock of approximately 40 Snow Geese ( a smaller member of the goose family) beyond the airport boundary while executing a missed approach at Montreal Airport, Canada. The number 4 engine was shutdown, and a safe landing was made. The number 3 engine controls jammed at idle during taxy. Damage was found across a 120ft span, greater than the engine spacing on the largest twin engined transport aircraft in service.
March 1999 a USA Jet Airlines McDonnell Douglas DC-9-15 encountered a flock of Snow Geese while on final approach at Kansas City International Airport. Several birds were ingested into both engines, resulting in severe engine power loss. The left engine suffered repeated compressor stalls and the other went to a sub-idle condition. The captain reduced the power on the left engine just enough to lessen the surge/stall condition and allow enough thrust to successfully complete the approach. This occurrence lead to a number of NTSB safety recommendations. One (A-99-087) was for the FAA to “in coordination with the U.S. Department of Agriculture, conduct research to determine the effectiveness and limitations of existing and potential bird hazard reduction technologies”. This was closed based on a 5 year work programme though no mention was made of investigating potential technologies.
One challenge air accident investigators face is that to even have a chance to be effective, safety recommendations need to be directed at an organisation with the authority to take action. This could be one reason why there has been a reluctance to make fairly general societal recommendations (on matters such as off-airport bird habitat and population management) to non-aviation organisations.
http://aerossurance.com/safety-manageme ... foresight/
Power of Prediction: Foresight and Flocking Birds
On 15 January 2009, two minutes after take off from LaGuardia Airport (LGA), New York City, US Airways Flight 1549, Airbus A320-214, N106US, encountered a flock of Canada Geese. The US National Transportation Safety Board (NTSB) investigation report says:
Both engines were operating normally until they each ingested at least two large birds (weighing about 8 pounds each), one of which was ingested into each engine core, causing mechanical damage that prevented the engines from being able to provide sufficient thrust to sustain flight.
Consequently the aircraft was forced to ditch in the Hudson River. The 155 passengers and crew members successfully evacuated the aircraft and were rescued with only 5 serious injuries.
The executive summary of the NTSB report covers many aspects of Crew Resource Management (CRM), training, ditching procedures / certification and survivability related to actions after a bird strike that prevent continued safe flight.
The NTSB summary only briefly mentions mention engine certification standards and wildlife hazard mitigations to prevent critical damage.
In this article we look at how hindsight from previous occurrences demonstrated the potential of such an accident and how prediction had shown the probability of a catastrophic bird strike outside the airport boundary was increasing.
Canada Geese: the Large Flocking Bird Hazard
Canada Geese (Branta canadensis), as a species are a major threat to aviation safety for there reasons:
Their large size (at an average of c8lbs+) means that a Canada Goose strike is at the top end of certification requirements for large aircraft
Their propensity to fly in ‘skeins’ (v-shaped flocks) which mean that multiple simultaneous strikes are possible
While traditionally a migratory bird, they have increasingly become non-migratory
Its this third factor that had been causing the risk of a double engine bird strike to increase. The NTSB published a chart of US Canada Goose population, which had increased from 1.2 million to 5.5 million over 38 years:
The nearly 20 fold increase in resident geese is significant as that means even greater exposure throughout the year.
This change in behaviour had come about because Canada Geese had increasingly been adapting to live year round in parks, golf courses and waterways in an around urban environments, while still flying in skeins to local feeding areas.
Readers of the NTSB report might conclude that this was something of a surprise to the industry.
Foresight not Hindsight and the Environmental Aspects of Bird Hazard Mitigation: Warning of Probabilities
In fact, among others, the UK Civil Aviation Authority (CAA) had been paying close attention to the threat of large flocking birds and the probability of a catastrophic a multi-engine bird strike. In a paper authored by Aerossurance’s Andy Evans, then a UK CAA Surveyor, the UK CAA warned that:
In some areas of North America, the risk of such an encounter may be approaching a critical level.
This was 8 years before A320 N106US lost power from both engines and ditched in the Hudson River.
At that time rule making to enhance engine bird strike resistance for new engines was already under way.
As there was little that could be done to enhance existing designs this paper was intended to highlight the critical need to take proactive environmental action to manage bird habitats.
While this included measures on and close to airports it also crucially included wider actions involving non-aviation stakeholders, the UK CAA paper endorsing a set of recommendations from the Aerospace Industry Association (AIA).
Although the Flight 1549 bird strike occurred beyond the range of the airport’s wildlife hazard responsibilities, the NTSB’s only environmental safety recommendation (A-10-75) after the Hudson ditching was focused on airports. This recommendation was directed to the Federal Aviation Administration (FAA) to ensure all US Part 139 US airports had conducted a Wildlife Hazard Assessment (WHA) and implement, if needed, a Wildlife Hazard Management Plan (WHMP). Completely contrary to the basic concept of a Safety Management System (SMS) and risk management principles a WHA is still today only required after a ‘triggering event’ according to 14 CFR 139.337 and this recommendation remains classified as open by NTSB.
One press report states that the Port Authority of New York and New Jersey (PANYNJ) has killed 70,000 birds between 2009 and October 2016. Just 1,830 were Canada Geese, with the majority much smaller birds. The really powerful risk mitigations remain those to manage bird habitats in urban areas.
Meanwhile Aerossurance is aware that, we think bizarrely, the concept of ‘Prediction’ is actually going to be removed from the next revision of the ICAO Safety Management Manual to leave just ‘Reactive’ and ‘Proactive’ approaches. Having three categories is allegedly seen as “too confusing” apparently. We think that’s a retrograde step.
But Not Forgetting Hindsight: Warning of Consequences
Some readers might be sceptical that even though it was being discussed around a decade before the Hudson River ditching, the aviation industry and wider stakeholders could really be expected to see the significance of the rise in the Canada Goose population before a major accident (in the same way that WHA’s are only required after the first ‘triggering event’ at an airport).
However there had been noticeable accidents and serious incidents involving geese in the late 1990s, listed in the UK CAA paper, that had been sufficient to trigger engine certification rule making:
June 1995 an Air France Concorde struck Canada Geese while landing at John F. Kennedy International Airport. Two of the four engines caught fire and were destroyed. Air France sued the airport operator. The case was settled trial for a reported USD$5.3 million.
September 1995 a US Air Force (USAF) Boeing E-3B crashed on take off in Alaska killing all 24 on board. The investigation concluded that the probable cause was the ingestion of Canada Geese into number 1 and 2 engines after they had been disturbed by a previous aircraft’s take off.
January 1998 a Delta Boeing 727-200 made a safe landing in Houston, TX after all three engines were extensively damaged, as were the leading edge slats, radome and airspeed pitot tube after striking geese at 6000ft in the climb
September 1998 a United Boeing 767-300 struck a flock of geese just prior to touchdown at London Heathrow. This caused extensive to the left hand side of the aircraft. This occurrence lead to a number of AAIB safety recommendations.
November 1998 a British Airways Boeing 747-100 encountered a flock of approximately 40 Snow Geese ( a smaller member of the goose family) beyond the airport boundary while executing a missed approach at Montreal Airport, Canada. The number 4 engine was shutdown, and a safe landing was made. The number 3 engine controls jammed at idle during taxy. Damage was found across a 120ft span, greater than the engine spacing on the largest twin engined transport aircraft in service.
March 1999 a USA Jet Airlines McDonnell Douglas DC-9-15 encountered a flock of Snow Geese while on final approach at Kansas City International Airport. Several birds were ingested into both engines, resulting in severe engine power loss. The left engine suffered repeated compressor stalls and the other went to a sub-idle condition. The captain reduced the power on the left engine just enough to lessen the surge/stall condition and allow enough thrust to successfully complete the approach. This occurrence lead to a number of NTSB safety recommendations. One (A-99-087) was for the FAA to “in coordination with the U.S. Department of Agriculture, conduct research to determine the effectiveness and limitations of existing and potential bird hazard reduction technologies”. This was closed based on a 5 year work programme though no mention was made of investigating potential technologies.
One challenge air accident investigators face is that to even have a chance to be effective, safety recommendations need to be directed at an organisation with the authority to take action. This could be one reason why there has been a reluctance to make fairly general societal recommendations (on matters such as off-airport bird habitat and population management) to non-aviation organisations.
Even bland can be a type of character