FLX C-210 Lands on Highway

Wow, that is a really busy road too. Mad props to that guy for being able to do that during rush hour.
 
Wonder if that qualifies him for the e-ticket upgrade to the Baron?
grin.gif
 
I wouldn't put it on my resume, but he'll definitely have something interesting to tell about in future interviews!
 
Considering it was FL, good thing it wasn't a toll road. I know I don't cary exact change in the plane.....
 
And this is suprising that a FLX plane lost it's engine? haha.


Great job... thats quite the airmenship and a bit of luck to not scratch the plane, himself, or anything else in that situation.
 
Yeah, what do you think the chances are that this guy did a good preflight inspection and a complete runup? If he did both, then kudos to him, if not, then shame on ya!

That being said, if you do a good preflight and a good (non-rushed) runup you should never have a problem. I read somewhere that most engine failures occur in the first 10-15 minutes the engine is in operation.
 
I'm guessing "no" on the run-up. I've seen some of these guys take off in Orlando, and they'll get departure clearance and cleared to take off while rolling through the run up area. I HAVE seen a couple of them stop and do run-ups, but they are the exception.
 
[ QUOTE ]
I'm guessing "no" on the run-up. I've seen some of these guys take off in Orlando, and they'll get departure clearance and cleared to take off while rolling through the run up area. I HAVE seen a couple of them stop and do run-ups, but they are the exception.

[/ QUOTE ]

It's pretty easy to do a rolling run-up.

Not saying it's always the best thing to do, but you can. I wouldn't do it on the first flight of the day . . .
 
Speaking of 210's... A few weeks back, a guy flying into Deer Valley, went down on the freeway. I haven't heard an official story, but it looked like he tried to land on the Northbound lanes, clipped the back end of a lumber truck, which inturn COMPLETELY ripped off the front of the airplane from the wing root forward, scattering wreckage about 200 yards up the freeway. Amazingly the guy was not killed on impact, but was in Critical condition the last time I heard.

I also heard that he had called into the tower about 20 miles out saying he was having engine trouble. Unfortunately, he continued to make his way to DVT rather than divert, landing as soon as practicable.

Ooo... here is the NTSB report
 
[ QUOTE ]
Yeah, what do you think the chances are that this guy did a good preflight inspection and a complete runup?

[/ QUOTE ]

[ QUOTE ]
I'm guessing "no" on the run-up. I've seen some of these guys take off in Orlando, and they'll get departure clearance and cleared to take off while rolling through the run up area.

[/ QUOTE ]

Yeah, and what do YOU think the chances are that he would've noticed any problems in the runup, since he was APPROACHING THE AIRPORT FOR LANDING when it happened.

I'm glad you two geniuses are so high and mighty and •! hot that you can skim right over the point of the post- THAT IT WAS A JOB THAT WAS DAMN WELL DONE and turn it into some sort of highly speculative monday morning quarterbacking session. You think you could've pulled off the same thing without a scratch on the plane, yourselves, or anyone on the ground? This dude had some serious odds stacked against him- low ceilings, congested area, wires all over, rush hour traffic.

But yes, you're right. It's probably his fault to begin with
sarcasm.gif
.... Please.
rolleyes.gif


By the way, one good runup for the first flight of the day is fine. If you're flying the same airplane all day, you really don't need to do a full runup before every takeoff, except maybe a quick mag check. It's really redundant outside of the training environment.

rolleyes.gif
 
[ QUOTE ]
since he was APPROACHING THE AIRPORT FOR LANDING when it happened.


[/ QUOTE ]

The only reason I brought up the run-up issue was because "The pilot, Jeff Cabell, said he had JUST TAKEN OFF FROM CRAIG AIRPORT on its way to Orlando when the engine began running rough. He notified the Craig tower that he was turning around to return to the airport, but didn't make it that far." To me this sounds like someone who just took off. When I was flying out of that airport all last summer I saw some operations there that were notorious for never doing run-ups.

Not trying to be a monday morning quarterback but I would like to learn from other's mistakes along with their correct actions that ended up saving the day. Like I said, I am fairly familiar with the Craig airport and also know that the road he landed on is always packed. How he got that thing down without damaging anything is amazing and I seriously DOUBT I could do it during an average rush hour there.

Bottom line: I could have worded my comment a bit differently and you could have been a little nicer the way you handled yours.
 
[ QUOTE ]
Bottom line: I could have worded my comment a bit differently and you could have been a little nicer the way you handled yours.

[/ QUOTE ]

No, that isn't the bottom line at all. Although I apologize, I didn't realize that he had just taken off. My bad for speed reading that.

The bottom line is, give the guy the benefit of the doubt before you first assume that he did not in fact do a runup, and second go blasting him for not doing one, which may or may not (probably not) have showed signs of an impending engine failure anyways.

Tell me, what might he have seen during a runup that would suggest a catastrophic engine failure? A bad mag? No. An airplane will fly on one mag. A prop governor issue? No, an airplane will fly with a messed up governor. Engine gauges out of the green? Probably not.

I used to instruct in a 182RG. One morning after I had flown it the night before with no indications out of the ordinary, the mechanic came in and said, "you gotta see this!" During the 100 hr. inspection, metal was found in the oil filter. They pulled the cylinders, to find that a 1.5 inch by 1 inch chunk had broken off the bottom of one of the pistons. It was sent somewhere for analysis (Lycoming or an independant metalurgist, can't remember now) who said that it was lucky that the whole thing didn't completely come apart, probably causing the engine to throw the rod and...who knows what else. Once again, there was NOTHING out of the ordinary in the way the plane ran or the engine instruments, yet that was still a catastrophic engine failure waiting to happen. I used to have pictures of the piston with the chunk missing, but they were lost on my old hard drive.

Anyways, my point again, is don't go speculating and give the guy the benefit of the doubt. Spouting off about not doing runups being the cause is just BS and speculation.
 
FYI the guy posted on flightinfo:

[ QUOTE ]
Thanks for the great posts guys. Believe it or not that was the second IO-520 to blow up on me. Same thing about 7 years ago in a C-210 in Colorado (luckilly VMC over farm country). Both cases could have been worse. My hats off to all single-engine night/IMC operators. Unfortunately most of us are forced to take the risk to gain the experience we need. Two branches of military service and 2000 hrs of HELO and the Centurion has almost gotten me twice. I'm just so glad no one (INCLUDING ME), got hurt. I'm going back to the turbine world ASAP!


Fly Safe,
Jeff

[/ QUOTE ]

I agree with ESF on the runup issue. Our school had a few students mess up soft-field landings and instructors had to ride with an FAA safety guy (NOT a 709, just a friendly CYA for our school, seriously). Anyhow, it was my turn and I walk up to the plane, the FAA guys says "it's already preflighted" and as I taxi down to the runup area he says "the runup's done" and we take off. Not saying that the FAA, especially the safety guys, are god but c'mon. If you've just flown the thing I'm not wasting my time doing a runup unless I see or feel something out of the ordinary.

~wheelsup
 
[ QUOTE ]

I'm glad you two geniuses are so high and mighty and •! hot that you can skim right over the point of the post- THAT IT WAS A JOB THAT WAS DAMN WELL DONE and turn it into some sort of highly speculative monday morning quarterbacking session.

[/ QUOTE ]

First off, Marsh: get off your own high horse. Show me ANYWHERE in my post where I said that would have caused a problem or if he had been able to detect a problem at that point. I stated what I knew and what I had observed. Never did I question his piloting abilities (which are DAMN good) or declare that he should have caught the problem during the runup. I'd really appreciate you NOT putting words in my mouth (or in my posts in this case).
 
I'm not on a high horse. It's actually a swivel chair with a messed up back.

[ QUOTE ]
I stated what I knew and what I had observed.

[/ QUOTE ]

Which was 100% irrelevant to the point of the thread.
 
[ QUOTE ]
Which was 100% irrelevant to the point of the thread.

[/ QUOTE ]

Granted, then again half (or more than half) of the threads around here go off relevancy. Doesn't give anyone the right to jump all over anyone's case for something they didn't say.
 
You didn't have to say it directly. Since you even posted it in the thread, it was implied.

But whatever. Sorry for getting on your case, it just kinda struck a nerve.

I'll play nice now.
smile.gif
 
You must log in or register to reply here.
Back
Top