Hello

I bought, installed and used the A2A Cessna 172 plane today. All went OK.

Then I let the plane alone for 3-4 hours, came back in the evening and had problems starting.

Eventually I started it but I was (and still am ) unable to stabilize RPM. Engine coughs when I push throttle > ~30 to 40% or more.

Problem persists even after I changed spark-plugs, overhauled engine, and reuturned the A/C to "new"condition.

I read the pilots manual and I followed the checklists. Posted a Q at A2A site forum but I dont know where my posts go there; I cant see them.So I am trying AVSIM since I have run out of ideas and had to keep this plane in the hangar. 

I would appreciate ideas of how to fix the problem..

Rgds

Alvaro Escorcia

 

 

I had a different problem after installing the Core v1.6 update ... but it sounds like your situation is a mixture problem or maybe carb heat issue?  What is the temp/barom reading?

Alvaro,

 

It sounds like your automixture may be on in your FSX realism settings?

 

Take a look at our FAQ here:

http://www.a2asimulations.com/forum/viewtopic.php?f=108&t=35640

 

Scott.

Are you starting out at a high elevated airport ?

Use SHIFT + F7 and let the hangar tech take a look at it.  

All

 

(1) Yes my problem is different that the one Rob had, based on what he says and  on what (I think) I read about his issue of having the plane stuck on the ground after installing the latest A2A Accu-Sim core update (A2A support forum) . More on that below, however.

 

(2) Auto-mixture is set to manual, in fact I moved that a lot via the Saitek control unit trying to fix my problem.

(3) Airport is at barely 200' above sea level, KSGR in Texas.

 

I found my post later in the A2A support forum. They recommended I install the latest A2A Accu-Sim core update. But looks like that one created a problem to some people re-surfacing previously fixed issues. Rob's case for example.

 

So, I have not installed the upgrade yet hoping to hear more from the AVSIM community....

 

And thanks a lot for the ideas coming up in this post...

 

Regards

 

Alvaro Escorcia

Make sure you go to the engine maintenance page within the maintenance hangar - sometimes it doesn't directly indicate a problem with an engine component on the main hangar page - I had a problem with cylinder #2 not holding pressure that showed nothing wrong on the hangar page, for example.

Hello,

 

please make sure you update to the latest v1.6 core update. Whilst Rob as you noted had an issue (now resolved) he was one of only two out of the thousands with an issue. We believe it to be directly related to the users saved flight. A change of the saved flight and Rob is now able to use the simulation trouble free.

 

"(2) Auto-mixture is set to manual, in fact I moved that a lot via the Saitek control unit trying to fix my problem."

I don't understand this the mixture settings and other required settings are FSX settings. You can see the required settings from the manual located under your start menu >> All programs >> A2A Simulations

 

Also have you performed any maintenance or a preflight? The engine will cough and splutter for example if you missed a rag in the intake or something else during pre-flight. 4-6 hours when you left the aircraft from working to not working is plenty enough time for someone to walk over to your parked aircraft and leave a rag or have a tinker with something they shouldn't.

 

And lastly, have you tried turning accu-sim damage OFF via the shift-3 panel?

 

thanks,

Lewis - A2A

 

 

I found my post later in the A2A support forum. They recommended I install the latest A2A Accu-Sim core update. But looks like that one created a problem to some people re-surfacing previously fixed issues. Rob's case for example.

So, I have not installed the upgrade yet hoping to hear more from the AVSIM community....

 

Since we're trying to fix your problem, not Robs, I'd say go ahead and install the upgrade.  If you end up with the same problem Rob has (unlikely) then we can work on fixing that.

 

EDIT:  I see Lewis has already posted on this while I was typing.

 

Hook

Use SHIFT + F7 and let the hangar tech take a look at it.

 

SHIFT F7 did nothing. Do u mean SHIFT 7? I did that from the beginning

 

 

"(2) Auto-mixture is set to manual, in fact I moved that a lot via the Saitek control unit trying to fix my problem."

 

I don't understand this the mixture settings and other required settings are FSX settings. You can see the required settings from the manual located under your start menu >> All programs >> A2A Simulations

 

Means I had selected auto-mixture to manual. The comment about changing it is because I had it in Manual. Thanks.

 

 

Also have you performed any maintenance or a preflight? The engine will cough and splutter for example if you missed a rag in the intake or something else during pre-flight. 4-6 hours when you left the aircraft from working to not working is plenty enough time for someone to walk over to your parked aircraft and leave a rag or have a tinker with something they shouldn't.

 

As I said above, I took the A/C to Hangar before attempting the flight. And I even reset the A/C to New. I understand that doing those 2 things should leave the plane as it says: New condition. Is there any other way?

Alvaro,

 

First, just go ahead and apply the v.1.6 update.  We're looking a 1/10th of 1% reporting problems, which is a very good number.

 

If you ever get stuck go to the external view and see if you can hear the engine.  if not, try CTRL-E (autostart) and see if that gets it running.  If it does, then this tells us that something is not being properly initialized at load which may point to a corrupt flight being loaded as default.

 

Scott.

.... my 172 spends more time at the repair shop then flying .... got only 7 hours and already encountered brakes problems, fuel & oil leaks, change spark plugs oil & filters, fixed the aileron and some other things that I'll see on the Big Ticket I'll get from the Repair Shop ... lol  ....this little Bird is Uber sophisticated  ...... startup is an issue, as well as some buttons that refuse to properly, comply with some of my GoFlight and Saitek's modules .... put on 'Navigator" for sale and moved back to my loyal Bonanza F33A  .... LOL

 

I think A2A came with a great idea implementation is not easy, and overall need to mature  

 

Cheers

.... my 172 spends more time at the repair shop then flying .... got only 7 hours and already encountered brakes problems, fuel & oil leaks, change spark plugs oil & filters, fixed the aileron and some other things that I'll see on the Big Ticket I'll get from the Repair Shop ... lol  ....this little Bird is Uber sophisticated  ...... startup is an issue, as well as some buttons that refuse to properly, comply with some of my GoFlight and Saitek's modules .... put on 'Navigator" for sale and moved back to my loyal Bonanza F33A  .... LOL

 

I think A2A came with a great idea implementation is not easy, and overall need to mature  

 

Cheers

 

 

You must be pounding on your 172.   I hardly ever have anything go wrong, other than I wore a few flap hinges loose doing many touch and goes over months; and I started with a used plane with 1000 plus hours on the engine!

.... my 172 spends more time at the repair shop then flying .... got only 7 hours and already encountered brakes problems, fuel & oil leaks, change spark plugs oil & filters, fixed the aileron and some other things that I'll see on the Big Ticket I'll get from the Repair Shop ... lol  ....this little Bird is Uber sophisticated  ...... startup is an issue, as well as some buttons that refuse to properly, comply with some of my GoFlight and Saitek's modules .... put on 'Navigator" for sale and moved back to my loyal Bonanza F33A  .... LOL

 

I think A2A came with a great idea implementation is not easy, and overall need to mature  

 

Cheers

 

Did you ever post over at our support forums? No other users have encountered the things you have there unless of course you are really trashing the aircraft or started with a sketchy used model which is simulated. Regarding the Go-Flight and Saitek stuff, this just has to be correctly configured. Details can be found at our support forums and please post any questions you have there too as its the best place for direct support from us and also the community helps out by being able to answer common questions and what not.

 

thanks,

Lewis

If you ever get stuck go to the external view and see if you can hear the engine.  if not, try CTRL-E (autostart) and see if that gets it running.  If it does, then this tells us that something is not being properly initialized at load which may point to a corrupt flight being loaded as default.

 

I actually get the engine to start relatively OK ( 1 of every 5 attempts ) using the standard procedure. Always I can start the engine with CTLR-E. The problem is that I cant get the engine above 25% of 30% of throttle (with any mixture setting ) without major engine coughing. I also see the visual throttle in the panel jumping pretty fast between hi and lo when Y push it forward. And of course the plane barely moves forward on the taxi way; I hardly can get it to start moving with the lack of power.

 

I am going to follow the recommendation and install the new AccuSim core patch and hope this resolve the problem. Otherwise, I suppose one could uninstall the product completely and try re-installing it again from the downloaded file.

 

Thanks for the responses

 

Alvaro Escorcia