Years ago, I took 3 hours of aerobatic instruction in a Cap 10 to experience spins, loops, inverted flight, etc., since spin entry and recovery is prohibited in the PPL curriculum.
Each country likely has its own set of regulations. In Italy, when I earned my pilot license, at the end of the course and prior to obtaining the rating, my instructor demonstrated a spin in the Cessna 152 and taught me the correct recovery procedures.
However, very few aircraft in Flight Simulator have a flight model that realistically supports this maneuver. I was hoping that the 152, being the âflagshipâ aircraft of the sim, would feature a top-quality flight dynamics model.
The 152 is the âflagshipâ aircraft? I almost thought it was forgotten! A little hidden thing behind everything elseâŠ
But I agree that it should be a flagship aircraft!
Thatâs what Iâve heard, but Iâm in Canada and have done a could couple of spins in training, whereas in the sim itâs close to impossible.
The text on the dashboard in the plane is still blurry, I raised this issue after launch and Iâm disappointed to see it hasnât been resolved.
Related to my feedback on the 172; the 152 has issues with proper implementation of switches from the Logitech switch panel. Specifically, turning on the Pitot Heat switch appears not to work â but then activating other switches may make it go âonâ. And activating additional switches may make it go âoffâ again! Completely broken logic somewhere in the aircraft systems implementation of switch input from a peripheral. I donât own Honeycomb gear to test with, but I suspect it might be broken with Honeycomb gear as well; in the 172, the Avionics Master switch is broken with both Logitech and Honeycomb gear, so it may simply be a fault in handling external inputs. The switches are fine using just the mouse in the virtual cockpit.
Just another in the long list of things which should have carried over from 2020, but are broken in 2024.
After SU3 this issue still exists even though a few things were fixed with the 152 (non-aerobat), you can only read text when youâre close to the panels
I know, the Cessna C152 Aerobat is not the best aircraft choice for a night flight. But is it normal, that the cockpit is so extremely bright? I am in the deepest desert, at midnight, with a black moon and no cockpit lights enabled. Even the flashlight is not active. ![]()
![]()
Why has the ADF not been fixed? Itâs been almost a year⊠Just mapped the cockpit to my hardware, currently on SU4 beta, and the ADF is totally black ![]()
Who needs to be asked that question. It is not at all clear WHO the developer of the C152 (& C172) is, or did I miss that info somewhere..
ie WHO is the one to FIX these C152 & C172 issues ??
That is an interesting philosophical questionâŠ
The plane is listed as Asobo C152, but Microsoft is the publisher and owner of MSFS. As an end-user, should I really need to bother with who they outsourced development to?
Considering some developers provide updates and even are open to feedback/questions about the aircraft theyâve created for MS, I think itâs useful information. Better to have it and not need it than to need it and not have it.
Sure, direct contact with the actual person(s) who made something is useful if youâre ultra-hardcore in the specifics youâd like to influence; but it should not be needed to get a standard instrument panel unit to work consistently? The end-user should not need to take the role of the producers and project managers⊠?
And I never suggested that they should only that they should be able to if they are so inclined. Of course regardless of the specific developer for an aircraft, issues for any default aircraft can and should be reported here on these forums first and foremost. There is nothing lost by providing users with a bit of additional information and context.
Hey guys, can you confirm that the cockpit of the default Cessna 152 is still extremely bright, even though the lighting is completely switched off and the aircraft is parked in a completely dark location at deep night, without any external light? ![]()
![]()

