Just trying to think of some other reasons. Is the plane heavier than normal? Is the runway sloped down? Is the runway paved and dry? How is the density altitude?
Basically, is it behaving worse than what you might derive from the performance charts for the conditions you’re in?
FWIW I’ve seen on other threads that braking action has been intermittent, despite controller bindings, etc. I myself have had flights in the 2024 VisionJet where I had toe brakes on landing, and the next day not. Could be a 2024 thing they are sorting out?
Maybe the brakes package didn’t load. Heh. Maybe it’ll be part of a DLC.
Nope, it should not. I’ve got a combined time of ~150 hours on the 172S and 172RG, I recognize conditions for longer landing distances. None of them apply here.
Dry, level, paved runway, roughly sea level, reasonable weights for landing (though technically it should barely make a difference), even employing short-field techniques still has me overrunning 2000’ runways.
Understood. I haven’t had the same issues so I wonder if it’s like what @Nikita is saying, that there’s a problem loading the brakes module.
Or maybe the wind is mid-registering on the G1000 and it’s actually a tailwind. I’ve seen some really wonky stuff with that.
There’s something weird with the braking. I constantly lock the left wheel and not the right even with same pedal travel in the animations. It also turns horribly on the ground too. I can pull much tighter turns in a Skyhawk IRL.
I agree 100%. I’ve found that using intermittent half braking (differential, of course) works best to turn tight after a backtaxi on a narrow runway. Much harder than in real life.
Anyone else confirm that the basic 172 is working now?
It does for me, but it never didn’t work for me. I tried it the first time last Saturday evening.
You can change that in the camera settings. Default is at 50, I put mine to 65. It feels a little high, but I haven’t bothered to tweak it further. I have 65 set for all planes.
thanks. I sorted out my issue.
My joystick also has the rudder axis assigned to twist action. Deleting it and keeping just my rudder pedal assigned to rudder axis active solved the problem.
Does anyone know how to change the altimeter baro from Qnh to InHg in the classic model?
Just to confirm, I tried the cessna 172 basic once again last night from cold and dark on the apron, and indeed no electrical power. Can’t start the engine
Yes, I saw the same, the fuel gauge moves now, regardless of electrical power, but the engine still won’t attempt to start.
I confirm that
I hope most G1000 problems are related to the same electrical problem and soon we solved, including G1000 inability to autotune NAV to ILS frequency on approach
How many levels of flap should there be in the 172? UP, 10, 20, FULL.
As I was finding I could move the lever to about 5 or so positions the other day, my lever was going to a position between UP and 10.
IRL years ago, the flap lever is continuous, albeit with a notch. In practice, flaps 10 downwind, flaps 20 turning base, and full flaps on final. Or something like that, as the situation dictates.
Historically, the 172 did have a max of 40 degrees of flaps (though I recall correctly, the full 40 would cause some handling issues).
It was around the M/N revision when Cessna swapped the toggle for an indexed flap configuration (flying C-GDDK back in July 2022 around CYHU via the ‘pilot for a day’, the CFI from the Saint Hubert Flying College noted ~3 seconds per index of flaps of holding the toggle)
The M model config (though it does seem odd in this file photo, how the altitude indicator was not replaced in tandem with the Directional gryo, which could have resulted in a vacuum system deletion. For ref, the Directional gryo has been replaced with a G5)
Compared to the R/S models
Edit; Apparently the 172M did have 40 degrees of flaps available (not sure when the 40 was phased out to max 30, Cessna 172M 40 degree flaps | Pilots of America)
Autopilot overshoots turns in both heading and nav, PID values need returning.
In FLC mode the nose up and nose down buttons should work the opposite way, as in nose down increasing speed and nose up decreasing it.
RNG knob is also working the wrong way, turning it to plus should expand the map range, not zoom it in.
Completely broken north up, trk/hdg up map settings, their menu entries don’t match the setting.
Need to move the throttle up halfway to have the slightest rpm increase