Thanks for posting this!Had a very close call yesterday, and still trying to process it and keep replaying it in my mind.
Thanks for posting this!Had a very close call yesterday, and still trying to process it and keep replaying it in my mind.
I agree, but you're making assumptions that don't seem fair. If you took off for a post maintenance flight and saw 500 degrees EGT climbing out, would you still continue to climb to 5k for troubleshooting, or would you do a single lap and get it back on the ground for troubleshooting? In this case we took off, saw something was immediately wrong and decided to investigate it on the ground. Maybe I described the situation poorly, but jumping straight to chastising me for only doing 3 minutes MX checks and not climbing fast enough seem overly harsh.
Instead we have thread drift.Blaplante,
Right on.
Your comment deserves real follow through.
Daddyman58
Instead we have thread drift.
Interesting that you know the "Achilles heel" of Lancair 36o's.Try this in a Lance. Lancair 360 little tail. Good luck.
Had my UMA made ASI (Vans Aircraft ASI) get stuck at 135 knots last summer while cruising to KPWT. Noticing no change in airspeed while slowing into the traffic pattern, I tried tapping on the ASI, but it remained stuck at 135 knots. So, we used GPS ground speed, accounting for the headwind component to achieve the desired airspeed into KPWT (desired approach airspeed = GPS ground speed + headwind component). Once on the ground, the ASI needle suddenly popped back to zero. Returning to KPAE after lunch, the ASI needle got stuck once again at exactly 135 knots. So, we did the same thing while landing at KPAE. I don't have a stall buzzer or AOG, but I thought about this possibility some years prior and had a plan. Before flying again, we sent the defective ASI to UMA for repairs, where they found the issue, fixed it, cleaned the movement and sent it back free of change.The challenge is less about flying with no ASI, it's having the ability to ignore what looks like a working ASI that is giving you bad information. Easier said than done.
Thread drift?Instead we have thread drift.
I now think I was getting un reliable information for a while. The big change was I was coming into a short strip that I wasn’t entirely comfortable with, even though I practiced short field the day before. Was so focused on landing at minimum airspeed, and I backed myself into a corner. Hindsight is very clear. I’m happy we came out of it unscathed. This is with 1000+ hours in type. It can happen to any (most) of us. Be careful out there guys.When driving transport Cat A/C we always practised unreliable AS in the Sim using…. pitch+ power= performance, even though I’ve retired I still practice this in the RV, worth keeping that skill sharp especially in todays high tech cockpits of GA light AC![]()
...if in doubt go around....
I’d modify this. If in doubt and have no specific reason against doing so, go around. Go arounds are not free. Yet we treat them as if they are. This is a mistake. Go arounds create their own risk, it is usually just that this risk is lesser or perceived to be lesser than the risk of continuing. When such is lesser, good. When it is merely perceived as such, mmm.
I’m really not a fan of “you can always go around.” Nope. I don’t really like that little tune singing such that is out now. It is, however, usually less risky. Difference in this way of thinking. Not as catchy a jingo either. Note a go around crash is more likely to be fatal than a landing crash. You may have doubt about other things while you may be clear that a go around is not good. It is rare, but such happens. You can have that skeptical sensation yet already know the out isn’t available. The out not being available might even be cause of the sensation, which kind of stinks, as this means you don’t know if that sensation is trying to tell you something else. What sucks is if you have doubt and also you are uncertain about go around capacity. Then you’re forked, you’re in the horns, Kobayashi Maru.
I am sure with that 787 that in the sim they’ve given you scenarios with no go around option. And I’m also sure they’ve given scenarios with that doubt all around trying to pick the least bad while not having full means to determine least bad option. Which makes a nice segue for Klein first fit pattern matching, recognition primed decision making (which often looks like non-decision instead just action), and Kahneman system one, Boyd OODA both the top loop and the normal loop. Which gets back to the rest of your comment, you need condition yourself with expected values, normal conditions and variances so as to have the patterns available to match even if you don’t recognize you’re thinking of them at the moment of need. WYSIATI.
I reckon...sounds like a lot of words to me. too many silly sentences. what would I know...24000 hours and i'm still here. done plenty of go arounds. only times I'd not be going around is if I thought A...we might lose the aircraft..(uncontained fire or the operating engine on fire and the other failed) B...low fuel situation and C... if it appears more dangerous than landing. Most of the time If in doubt....go around. it's a standard procedure and should not faze a practiced pilot. He is talking human factors 101 like we don't study them...yes all the decision making models....different for professional pilots practicing regularly than the fine weather pilot...if your engine is working and the weather ok....and you are not on fire or plugged yourself deep up a valley then a go around is probably the best course of action for the average weekend pilot.Talk about a word salad…
It reminds me off a story I heard about fly eggs being a nasty brown mass. Is it possible an insect found the static system to be a safe spot to lay eggs?In reading, before I saw the pictures, I was convinced something had settled in a low spot. But then the photos show a proper installation where the lines go uphill from *both* static ports. And something has been introduced from both sides. Huh? Paint prep something? I'd think EAA, Van's or someone would be interested in getting a professional analysis of those lines. With all the focus on LOC in the pattern, here we have evidence of something that could affect the fleet. We need to figure out what did that.
I've had two separate airspeed failures in my RV-9A -- one due to a bee flying into my pitot tube after takeoff, and another when my Vans UMA airspeed indicator stuck at 135 knots while slowing down from cruise. Ever since Phase 1 flight testing back in 2004, I always cross-check final approach speed with my WAAS GPS ground speed by adding the approximate headwind component to my GPS ground speed. I don't have an AOA or stall tab but have always used this method to cross-check my final approach speed. It's also a good idea to practice slow-flight and how it feels when it's getting too slow.
I think in the early days of glider flying in the US they had not gotten around to regulating gliders. Also in that era there was a question of what was legally a glider. The primary gliders were single seat towed behind a vehicle with the instructor sitting on the back of the vehicle and using hand signals to instruct the "student". So the first "flight" was actually the first solo. I am still searching for answers but it appears that solo flights well before age 14 were common.Some started in gliders, solo by 14.
Want to get in trouble for going around? Soar a thermal out of the landing pattern at 500'.