Two dead after Bonanza crash in KS

kiloalpha

Well-Known Member
http://www2.ljworld.com/news/2010/jul/01/reports-small-plane-crash-jefferson-county/?breaking

Two people were killed Thursday morning when the plane they were flying from New York to Arizona crashed in rural Jefferson County just north of Lawrence, Jefferson County Sheriff Jeff Harrig said.

The plane, a 1987 Beech Bonanza, left Hamilton Municipal Airport on Wednesday, arrived in Kansas City Wednesday night, before resuming its journey to St. John’s, Ariz., Thursday morning.

According to an audio recording of air traffic control traffic from Kansas City Center, the plane lost power to its engine and was trying to make an emergency landing in Lawrence Municipal Airport. The air traffic controller said the plane didn't have enough altitude to make it to Lawrence, and that the pilot saw a road where he was going to attempt to land.

According to FAA flight tracking data, the plane left Kansas City about 7:30 a.m. and headed west then south before abruptly turning back near Salina and heading toward Kansas City.

Louie Peterson, a mechanic at Hamilton Municipal Airport, said he knew the pilot of the plane to be an experienced pilot.

“He’s flown that thing all over the country,” Peterson said. “From Colorado to California.”

LJWorld.com is withholding the name of the victim pending notification of family members.

Peterson said the two deceased, a man and his wife, were en route to visit his sister in New Mexico. St. John’s, Ariz., is on the Arizona-New Mexico border.

Mike Jamison, owner of the nearby J Bar Ranch, witnessed the crash. Jamison was working in a field when the plane flew in from the north and crashed on his land.

"It was flying so low," Jamison said. "It caught some air and went down immediately."

After Jamison heard a crash noise he called 911. When he arrived at the scene, he said the pilot of the plane was unresponsive.

The Kansas Highway Patrol is leading the investigation into the crash, but the Federal Aviation Administration and National Transportation Safety Board are also sending representatives to the scene.

Check back with LJWorld.com for more on this story.

Turns out one of my friends heard this over center freq today... kinda sombering. RIP fellow aviators... :(
 
That's sad to hear. Why turn all the way around by Salina if you knew you had a problem? That was a long ways to fly over suitable airports to try to return to KC. RIP

"It was flying so low," Jamison said. "It caught some air and went down immediately." :confused:
 
That's sad to hear. Why turn all the way around by Salina if you knew you had a problem? That was a long ways to fly over suitable airports to try to return to KC. RIP

I'll second that thought. There isn't a plane in the world that couldn't land in Salina. Just land there and sort it out. This one scared me at first, because I know lots of people in Kansas with Bonanzas. In any case, RIP
 
That's sad to hear. Why turn all the way around by Salina if you knew you had a problem? That was a long ways to fly over suitable airports to try to return to KC. RIP

"It was flying so low," Jamison said. "It caught some air and went down immediately." :confused:

I took that as the nose came up abruptly and it stalled, but we'll see. Like the Salina report, this media stuff is usually very inaccurate.

Sad day.


EDIT: Nope. FA has them way west and doing a 180.
 
That's sad to hear. Why turn all the way around by Salina if you knew you had a problem? That was a long ways to fly over suitable airports to try to return to KC. RIP

Exactly what I was thinking... why the hell go all the way back to Lawrence?
 
Exactly what I was thinking... why the hell go all the way back to Lawrence?
What y'all said. Salina is suitable for about anything. I am thinking maybe there was more to the story? A prima facie it looks like a bad decision. Maybe they returned for other reasons and developed the problem later?
 
I'm not going to Monday morning quarterback this thing but it is just plain sad to hear.
 
This is a sad story. Sure is a shame these people had to lose their life. If they had went into Salina the problem could have probably been resolved, but either way, loss of life is terrible.
 
I've been looking at the flight aware track log and it's no good. The plane never, really got west of Lawrence. It climbed out ~280 course, something happened, he did a RH 270 to go to LWC and didn't make the field. It was 8 min from altitude and ground speed irregularities to totally corrupt data (loss of radar contact). There is no way to make it ~100nm in a perfectly normal F33 let alone one with a sick engine.
 
I've been looking at the flight aware track log and it's no good. The plane never, really got west of Lawrence. It climbed out ~280 course, something happened, he did a RH 270 to go to LWC and didn't make the field. It was 8 min from altitude and ground speed irregularities to totally corrupt data (loss of radar contact). There is no way to make it ~100nm in a perfectly normal F33 let alone one with a sick engine.

Why would the track even show up if they didn't make it that far? I don't recall ever seeing "false tracks" on Flight Aware. I do agree that the radar track and the log do not match, but which is right/wrong?
 
Why would the track even show up if they didn't make it that far? I don't recall ever seeing "false tracks" on Flight Aware. I do agree that the radar track and the log do not match, but which is right/wrong?


I know it has plotted some of my flights incorrectly, and I have seen some strange or missing tracks. Those are usually associated with "results unknown" or (sometimes) diversions. Also, to go 100nm (estimated point of course reversal point to LWC) in 8 minutes would require a ground speed of 750 kts. Didn't happen.
 
I know it has plotted some of my flights incorrectly, and I have seen some strange or missing tracks. Those are usually associated with "results unknown" or (sometimes) diversions. Also, to go 100nm (estimated point of course reversal point to LWC) in 8 minutes would require a ground speed of 750 kts. Didn't happen.

I understand that. I'm just playing devils advocate and suggesting that maybe the log is bad and the track is correct. Needless to say though, it always hurts to lose fellow aviators. May they RIP and condolences to the families.

EDIT: Looking again at the radar track, it looks weird. The entire western half of the flight route looks like it was filled in after the fact when as you said, the results came up unknown.
 
I just found this

According to FAA flight tracking data, the plane left Kansas City about 7:30 a.m. and headed west toward Perry Lake. Sometime before he crossed the lake, he made a turn toward Lawrence because of an in-flight emergency.


A short time later, he crashed along Phillips Road. An early report that he flew to Salina was based on an inaccuracy in FAA data.

Also, there appears to be only 16 minutes of data from radar contact to rc lost.
 
Back
Top