jkhirsch

Sorry for the ridiculously late reply here, some of the upgrades must have disabled my email notifications or something who knows. I do still have the stuff sitting in my garage. I don't have any idea what the stuff is worth.

I just want to reiterate how annoying skyvector is now. I used to goof around on there all the time, it's almost unusable to me at this point. Sure is a shame that people don't consider the trade offs when they make sweeping changes. I used to love the "drag and drop" waypoint functionality...and they killed it...built a drone with a heroin dart gun and a pistol, overdosed it and put on in the head for good measure.

I have been to Dry Tortugas on a boat and done the tour of Fort Jefferson, it's a pretty cool place to go. Would have much preferred a float plane to the hour boat ride. This was part of a motorcycle trip where we rode the keys, not sure which would be better flying or cruising.

I will actually be in Canton this weekend. Not sure if it will work out to come up for lunch or not. Any tally of Mooney guys being there?

Since we're already way off topic, looks to me like you need a big display for your charts so you can get that silly yoke mount out of the way.

That's that same old Liquid Rocket that's been drifting around aimlessly for a couple years. It's a liquid cooled double secret turbo charged engine, I've always assumed that tube played some part of the additional system. I think there's a long thread somewhere that talks about that mod and a bunch of other "fun" things.

Hank, according to the times provided there were approximately 5 minutes between when he was 34nm out and the collision. If he was flying approximately the speed limit 250kts then 200kts it would have taken him approximately 10 minutes to cover the distance direct to CHS. Upon further examination of the chart, it would appear that the fighter pilot was somewhat near the KIMMY intersection and may have even been following the Victor Route from MYR to CHS. I've attached a map courtesy of skyvector that would indicate the previous statement along with a direct clearance to IBANE. The bug comes in where a heading of 260 from KIMMY would not be direct to IBANE if he was on or very near the Victor Route, which is demonstrated by the little jig in the pink line. However a heading of 260 from KIMMY would lead very near the proposed collision site. Please understand that I am not pointing any fingers, I'm just speculating on this missing pieces of information right now.

Ross, it says they found the wreckage in/near the west fork of the copper river. I also fail to understand the disclosure of the speeds and whatnot. Obviously not a ton of detail as far as location of collision, but a close-ish guess. The west fork basically runs "right next to the airport" which would make sense for left traffic essentially making a u-turn to head northeast from 23.

There's a certain economic interplay here...if you want a rocket and there are only so many available, regardless of condition and owner can set his price. There's also a liquidity discord, how quickly does an owner want his money, versus how quickly do you want a plane. Lying is an entirely different issue of which I will not defend. I have adopted Bernanke's philosophy: become so transparent that people don't know what the hell to think.

I was going to start a new topic however this is so perfectly relevant. Picked it up on flightaware squawks this morning. http://www.cbsnews.com/news/gun-firing-drone-video-draws-federal-scrutiny/

map

Yeah I have no idea where this assumption that he was one the DME arc came from. Please correct me if I am saying something stupid here so I can go back and edit my post so it doesn't look like I said something stupid. In order for a collision to happen with the fighter on the DME arc the Cessna basically would have had to violate CHS airspace. Airspace 10nm = DME arc 10nm = Cessna Pilot would have been doing something wrong and going the wrong way. Also if he was on the DME arc his heading at the time of impact would have been 270 or greater based on the arc. Did you guys look at the map? When the controller advised traffic opposite direction, they should have been exchanging paths at approximately respective headings of 065, 245. With regards to a 23 departure from MKS then a direct to CRE.

I don't want to bicker, I didn't look at all the timestamps, but the ntsb initial said that the controller, 'had to repeat himself.'

Alright, I'm calling in for the edit on that post...too long! Great effect though.

I hate chiming in on stuff like this. That being said... The initial report does read like the fighter pilot did not correctly respond to the initial evasive maneuver assigned by ATC.

Just now realized how bad it actually is if you sometimes like to program in random intermediary points along the initial route. The simple ol` "list" functionality for "route construction" now looks really underrated/under-appreciated. Gee whiz...

Don't get me wrong.....I'm PaF. (highly upset)

I've used skyvector as long as I can remember. I was equally annoyed with the change to the "flight plan form" when I went on yesterday. Since the prior form already existed they should just offer a button that says, "simple flight planning" and "enhanced flight planning." I did figure out that you can still manually type a speed in. I'm not surprised by the change, just a bit disappointed. They had unparalleled simplicity, many times I just used to it see how far apart to various places were. I remember when skyvector didn't have the "World VFR" functionality, so not all change is bad...

Well gee whiz, sure am glad I missed the thread last week and the opportunity to register. I guess wait listed is as good as she gets...

I think it's a smashing idea. Especially considering you have indicated that he is doing it 'as a good friend.' I would be highly inclined to basically let him handle everything, and "send you a bill." Obviously you would want some input for your involvement.

Well if it's just your experimental.....

Aside from the first instinct of being incredibly greedy I think you can reasonably assert two things: Your plane will need to be repainted. You will be inconvenienced by the entire process. I would let them know that you expect reasonable compensation for both.

Man that paint job with the lines on that plane and the color on the prop matching the Swiss badge, that's a great looking Mooney.

I feel obligated to refer you to the sentence immediately following that one. Maybe I should have also included the old <sarcasm> tags on that part of that sentence as well.

Let me start out this post by stating the obvious: "Every single person looking to buy a plane would like to have an amazingly simple transaction on a beautiful "turn-key" airplane." I tend to believe that if something's worth having, it's worth working for. Therefore, I see no reason for everyone to instill this panic here; if it has truly been annual-ed by an MSC then everything should be in order. That doesn't mean I'm taking my cash briefcase over to the current owner, but it means I'm going to follow through with the due dilegence phase of a purchase. It basically costs nothing to have a different mechanic look at all of those photos and compare them to a logbook, or even better yet to have a mechanic out to see the plane in person and compare it to the logbook. Take the guy to lunch and you might pay zero dollars for his time.Then you aren't even in for an annual, you're just in for seeing if it even passes a mechanic's smell test, instead of a bunch of us over the internet. Let's remember a key point: There's no such thing as a bad airplane, just a bad price. If the seller is amicable and truly interested in selling then a simple conversation is absolutely worth having. What matters is that work is done according to AC 43.13 and documented correctly by the mechanic who did it, every other opinion is nonsense. If this thing is literally based on the field where you would base it you're crazy to "run" because the logistics are so easy to deal with. P.S. I also sent you a PM, maybe you didn't respond on purpose