philthehill wrote: ↑Mon Sep 19, 2022 6:40 pm
The runway has been shortened since the Vulcan flew in to Wellesbourne airfield, so it has very little room for high-speed runs.
Phil
They were using runway 18/36 for the high speed run which hasn't been shortened. It's still the length it was in WWII. The 'useable length' markings have been moved in, but it's still the same length of concrete & tarmac.
The official explanation for the overrun of the end threshold is that the Air Speed Indicator gave a false reading, despite being OK at the start of the run,
"which resulted in the aircraft remaining at full power for approximately 2 seconds longer than intended".
So they missed all the visual markers of where they would expect to cut the throttles.......
Were they relying on cutting power at an indicated airspeed, irrespective of how near the end of the runway they were getting?
Had they not briefed on all eventualities?
It's likely the most feeble excuse I've ever heard from a crew.
As an RAF aircraft engineer for 37 years, I can categorically state I have never known a Pilot admit to making any mistake, it's always some technical failure, no matter how outlandish.
I've know Pilots pull too much G while flying and they reset the cockpit G Indicator as when they sign the aircraft back in they are supposed to report it, because excess G has 'levels' and as those levels increase there are increasingly more stress and damage checks required.
Pilots are too dumb to remember that the ground crew, at every After Flight Servicing, record the Fatigue Meter Readings which tell the engineers exactly how many times the aircraft has been into each level of Positive and Negative G.
When you confront them with the recorded evidence, they still deny it and try to blame the Recorder...
I've even had to get an Accident Data Recorder downloaded to confront them with exactly when during their flight they pulled the excess G they are denying, and they get memory loss of the instance....

- Wellsbourne.JPG (93.55 KiB) Viewed 4420 times