Plane crash in Manassas, VA

Airdale

Well-Known Member
We've got a Dornier 328 turbo prop that went off the end of 34R here this morning. I've got a few pictures I took, but I have no info on what happened and whether or not everyone is alright. Anybody got any scoop on this? I'll try to post up a few pics of the incident later on.

It appears though, based on the scene and the photo's I took, that the aircraft had an engine failure during the take-off roll and could not stop in time, thus going off the end of the runway and skidding to a stop in the road jsut before railroad tracks. Maybe an engine failure before V1, but I thought V1 must include your accel/stop distance. Either way I don't have all the details, just hope everyone on board is okay.

Here's a photo from airliners.net of what the aircraft is, I can't tell if its the turbo prop version or the jet version that crashed.
1042574.jpg
 
Dude, you may want to say plane overruns runway...Crashing and overrunning a runway are a lil different unless the thing tumbled,etc.
 
Airdale said:
It appears though, based on the scene and the photo's I took, that the aircraft had an engine failure during the take-off roll and could not stop in time, thus going off the end of the runway and skidding to a stop in the road jsut before railroad tracks. Maybe an engine failure before V1, but I thought V1 must include your accel/stop distance. Either way I don't have all the details, just hope everyone on board is okay.
1042574.jpg

Before we all go off on some wild speculative "guess-a-thon" or brazenly begin Monday morning quarterback'n what the crew would've, could've or should've done and what you would have done in that exact scenario. Let's try to wait for some official report other than the local news media trying to hype a story.

Not pointing fingers at anyone...just my personal opinion.
 
A300Capt said:
Before we all go off on some wild speculative "guess-a-thon" or brazenly begin Monday morning quarterback'n what the crew would've, could've or should've done and what you would have done in that exact scenario. Let's try to wait for some official report other than the local news media trying to hype a story.

Not pointing fingers at anyone...just my personal opinion.

Dude, I wasn't "monday morning quarterback'n" as you put it, I'm giving an opinion on what I think happened based on this very big airplane sitting in the middle of the road just a few feet short of a set of railroad tracks at my airport. I doubt he ran off the runway trying to land. The runway here is rather lengthy and based on the position of the aircraft it looks like an aborted take-off run. Never said nor implied the pilot(s) screwed up, or what they did wrong or what they should've could've done. Just stating what I think happened reguarding the position of the aircraft on the road.
And yes I would call it a crash. They slid through a fence, down a hill onto a road and almost onto railroad tracks. If you're car slid through a fence, down a hill, across a road and almost onto railroad tracks, I think you'd be calling it a crash too. :) I believe when that Southwest 737 slid off the snow covered runway up north they considered that a crash. I mean the NTSB had a report on it. I would consider it a very minor incident though, nothing too serious. Here's a couple pictures.
Again, I'm not saying somebody screwed up, just reporting an incident here and how I think the aircraft ended up there.

73188824-M.jpg

73188839-M.jpg
 
Airdale said:
Dude, I wasn't "monday morning quarterback'n" as you put it, I'm giving an opinion on what I think happened based on this very big airplane sitting in the middle of the road just a few feet short of a set of railroad tracks at my airport.

Well, ah.."Dude", I said I wasn't pointing any fingers at anyone. Remember? ;) You seem to have taken it as a personal attack or something.

However, since you wrote:

Airdale said:
It appears though, based on the scene and the photo's I took, that the aircraft had an engine failure during the take-off roll

You have no idea how that airplane got there or what caused it to come to rest at that spot. You've made an assumption, without knowing any of the facts, that it had an engine failure and didn't have room to stop. Are you sure it wasn't landing? Maybe they had brake, hydraulic or flight control failure. Maybe the PF had a heart attack, seizure or spilled hot coffee on his lap at a critical time. Maybe a herd of buffalo crossed their path or whatever else someone can dream up at this point...

The point I was trying to get across is I've seen enough of these types of accidents or incidences where folks are quick to come to their own conclusions (mainly the media) simply based on what they see in front of them without knowing any of the real facts or what lead up to the accident.

I bet if 100 people read your original post, because that's what they SAW, the seed was probably planted right then in their head that "Yep, engine failure..went off the end, that's that, end of story." Heck, he even had pictures to boot! What else could it be? Then it morphs into something about unsafe "little jets" or puddle jumpers, they must have been drunk, PFT or some other hot topic which may nothing to do with the real cause. The only irrefutable fact right now, based on your pictures, is that an aircraft is sitting on a road. How and why it ended up there is the $64K question.

While we all want to know what happened in this day in age of instance information and analysis, I'm willing to wait for the experts to investigate and report. Just my opinion.
 
I was at Manassas airport today, and saw that aircraft resting like that.

A guy there told me that apparently, he heard on the radio something about erroneous airspeeds readings, which led to the aborted takeoff. Same guy also said that everyone walked away from it, so no major injuries. That's pretty much all hearsay, so I guess I'll wait for the NTSB report.

AirDale, you work at a Manassas FBO, if so, where?
 
Awww, Observation Rd. at Mo-Nassas airport... how I miss driving on you to get around the freakin' train stopped across the tracks or to buy charts a Mo-Nassas Aviation Center.
 
Day #1 of Bill Waldock's aviation safety class:

"Don't ever say "Ah, ha! This is what happened!" when you first walk onto the scene, chances are you're wrong" (very roughly paraphrased)
 
A300Capt said:
Well, ah.."Dude", I said I wasn't pointing any fingers at anyone. Remember? ;) You seem to have taken it as a personal attack or something.

However, since you wrote:



You have no idea how that airplane got there or what caused it to come to rest at that spot. You've made an assumption, without knowing any of the facts, that it had an engine failure and didn't have room to stop. Are you sure it wasn't landing? Maybe they had brake, hydraulic or flight control failure. Maybe the PF had a heart attack, seizure or spilled hot coffee on his lap at a critical time. Maybe a herd of buffalo crossed their path or whatever else someone can dream up at this point...

The point I was trying to get across is I've seen enough of these types of accidents or incidences where folks are quick to come to their own conclusions (mainly the media) simply based on what they see in front of them without knowing any of the real facts or what lead up to the accident.

I bet if 100 people read your original post, because that's what they SAW, the seed was probably planted right then in their head that "Yep, engine failure..went off the end, that's that, end of story." Heck, he even had pictures to boot! What else could it be? Then it morphs into something about unsafe "little jets" or puddle jumpers, they must have been drunk, PFT or some other hot topic which may nothing to do with the real cause. The only irrefutable fact right now, based on your pictures, is that an aircraft is sitting on a road. How and why it ended up there is the $64K question.

While we all want to know what happened in this day in age of instance information and analysis, I'm willing to wait for the experts to investigate and report. Just my opinion.

I didn't mean to sound rude. I was just speculating on how the airplane ended up there based on what I saw. I was in no way trying to determine the cause. Its kind of like when you drive past a car accident on the road, and you look over at the scene and try to determine who hit who or how that car ended up in a ditch. Its not trying to formulate a reason for the accident, just trying to figure out in your own head how it got there. From the Police officer I talked to, and photo's I took at the scene, it appears as though it was an aborted take-off. Sure I could be wrong, but I'm just speculating that to be the case. So I apologize if I came off the wrong way. Wasn't my intention.
 
Airdale said:
I didn't mean to sound rude. I was just speculating on how the airplane ended up there based on what I saw. I was in no way trying to determine the cause. Its kind of like when you drive past a car accident on the road, and you look over at the scene and try to determine who hit who or how that car ended up in a ditch. Its not trying to formulate a reason for the accident, just trying to figure out in your own head how it got there.

Yea, like you say, we all tend to look at a car/train/boat or aircraft accidents and try to piece together what happen and form our own conclusions. It's hard, I know, and It's only natural. I guess I've just studied airplane accidents enough to know not to jump to conclusions at first sight.

Anyway, no harm no foul. Good photos BTW! My current f/o use to be a Captain on one of those DoJets and really like them. He's probably one of the sharpest f/o's I've had the pleasure of flying with.
 
Interesting... the NTSB report doesn't list any crew on board. While we are guessing about what happened... how about the pax got tired of waiting for the crew to come to the airplane so they tried to take off them selves:whatever:
 
I was in VA this weekend... there was no engine failure.

The Captain's and FO's airspeeds did not agree, so rather than aborting right away, they argued about the abort past V1, and attempted an abort in ground effect with less than 2000 feet remaining.


Needless to say it didnt work out for them.... stupid stupid stupid. :whatever:

D
 
Cherokee_Cruiser said:
I was at Manassas airport today, and saw that aircraft resting like that.

A guy there told me that apparently, he heard on the radio something about erroneous airspeeds readings, which led to the aborted takeoff. Same guy also said that everyone walked away from it, so no major injuries. That's pretty much all hearsay, so I guess I'll wait for the NTSB report.

AirDale, you work at a Manassas FBO, if so, where?

:yeahthat:
 
danam404 said:
I was in VA this weekend... there was no engine failure.

The Captain's and FO's airspeeds did not agree, so rather than aborting right away, they argued about the abort past V1, and attempted an abort in ground effect with less than 2000 feet remaining.


Needless to say it didnt work out for them.... stupid stupid stupid. :whatever:

D

And how exactly would you know this. That seems like a pretty exact explanation to have. Were you in the cockpit, did you talk to the pilots, etc....That's a pretty bold statement to make. You should probably offer up some explanation as to how you know that instead if playing NTSB investigator.
 
WOW the guy made an guess as to what happend! And you guys jumped on him like a.net people or something.

I just hope everyone involved is ok, and the plane did not get much damage to bad.
 
Back
Top