Monday, 5 December 2016
YOU NEVER “HAVE TO” MAKE A GA FLIGHT!
Acknowledgements: AOPA & David J. Kenny
Fans of the British comedy troupe Monty Python share a particular fondness for the character of Ron Obvious, the first man ever to try to jump the English Channel.
“How far is it across the Channel?” asks an interviewer (John Cleese).
“Oh, about 21 miles from Dover to Calais,” replies Mr. Obvious (Terry Jones).
“And what’s the farthest you’ve managed to jump in practice?”
“A little over six feet.”
Sure enough, the record jump attempt proves … anticlimactic!
The sketch provided a particularly sly reminder that willpower and optimism come out second best when they take on the laws of physics.
In general aviation, this is proven the hard way year after year by a tiny minority of aviators who feel that an immediate need to complete the flight outweighs the very real risk that they won’t. Making the attempt in the face of known mechanical problems, hazardous weather, or simple inexperience can vastly increase the cost of not reaching that destination.
Consider the following accident report and decide what you would/would not have done ……
The Cessna stopped for fuel at Columbia, Missouri on the way from Jackson, Tennessee to Sioux City, Iowa. It took on 26 gallons. While on the ground, its pilot called to get a weather briefing for the final leg. The briefer advised that Sioux City was IFR and expected to remain so. Low clouds covered much of the route, including northern Missouri and western Iowa, with tops reported between 2,500 and 4,500 feet. Weather in eastern Nebraska was “beautiful,” but instrument conditions also were expected to develop there around his ETA; temperature/dew point spreads were already narrow and decreasing. The pilot responded that his job and vehicle were in Sioux City, so the briefer identified Wayne, Nebraska, 28 nautical miles west-southwest, as the nearest airport reporting clear conditions.
They discussed the option of flying VFR over the cloud deck, but because the pilot was not instrument rated, the briefer suggested flying northwest to Kansas City, then turning north on the west side of the Missouri River. He also recommending stopping at Omaha to reassess the situation. The pilot replied that he’d decided to fly direct to Sioux City above the clouds, diverting to Wayne if conditions required. The briefer advised him to get weather updates en-route and provided him with a list of the appropriate frequencies.
The Cessna took off at 3:40 p.m., an hour and a half before sunset. The moon had gone down in mid-afternoon. The pilot requested and received flight following. Around 6:30 he reported clear skies and good visibility above the clouds to the Sioux City approach controller. The controller asked him to “let me know when you get ground contact” and advised that Sioux City was under a 700-foot overcast. Wayne and Norfolk, Nebraska, still reported clear skies. The pilot responded that he was beginning his descent without ground contact, adding “I’m sure I’m getting fairly close,” and said he planned to land on Runway 36 at Wayne.
Descending through 2,000 feet, less than 600 feet above ground level, he still could not see the ground. The controller provided an updated observation from 10 minutes earlier that included a 200-foot scattered layer at Wayne. The pilot continued to descend, reporting negative ground contact at 1,800 feet. Acknowledgement of the loss of radar contact was the last transmission received from him.
The wreckage was found in a small area at the end of a short debris path, suggesting a steep angle of impact. The next METAR from Wayne, six minutes after the accident, listed the ceiling as overcast at 200 feet. Norfolk, another 25nm southwest, stayed clear with good visibility for two more hours.