Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

C152 JPL no Airspeed

Featured Replies

On 6/26/2023 at 11:08 AM, Alvega said:

Check all the circuit breakers.

I have not flown a real life c152 for about 25 years so my memory is hazy, but if I recall correctly the ASI worked by comparing pitot tube pressure with static port pressure and possibly worked with engine vacuum though I am not sure about the vacuum.  No electrics as far as I recall, but I may be wrong.

Sooo  ... pitot tube, static port and possibly suction would be the things to check in a real aircraft.

One thing that was always in the check list back then was the suction gauges that worked the gyro etc for vacuum pressure.

Edited by Glenn Fitzpatrick

  • Replies 33
  • Views 6.3k
  • Created
  • Last Reply
52 minutes ago, Glenn Fitzpatrick said:

I have not flown a real life c152 for about 25 years so my memory is hazy, but if I recall correctly the ASI worked by comparing pitot tube pressure with static port pressure and possibly worked with engine vacuum though I am not sure about the vacuum.  No electrics as far as I recall, but I may be wrong.

Sooo  ... pitot tube, static port and possibly suction would be the things to check in a real aircraft.

One thing that was always in the check list back then was the suction gauges that worked the gyro etc for vacuum pressure.

There's a circuit breaker for the beacon and pitot. That's the one that can cause the issue.

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

I'm having the same problem.

Everything else working, but no movement on airspeed.

 

Follow the checklist, Pitot heat on (just in case).  Circuit breakers are good.  Suction gauge in panel is mid-scale.

Tried restarting and rebooting but behavior is the same.

 

Hopefully tonight I can spend more time with it and toggle realism/state saving off from the tablet.

Might also be time to check Community folder for conflicts.

 

 

Best Regards,

Mark

 

i7 10700KF 3.8gHz -125W air cooled, 500W PSU, 4070 Dual OC 12GB, 32GB 3200, 43" P4317Q

Redbird Alloy RD1, Honeycomb Alpha, Bravo, Stream Deck, Quest 3

22 hours ago, Alvega said:

If airspeed doesn't work either you didn't cover the pitot when you left last session or you have a popped circuit braker.

Why on earth would a circuit breaker in a C 152 cause the airspeed indicator, which is driven by the pressure in the pitot tube, not read airspeed?

Edited by Bobsk8

 

 

 

17 minutes ago, Bobsk8 said:

Why on earth would a circuit breaker in a C 152 cause the airspeed indicator, which is driven by the pressure in the pitot tube, not read airspeed?

Perhaps because the pitot heat is not functioning? 🙄

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

2 minutes ago, Alvega said:

Perhaps because the pitot heat is not functioning? 🙄

OP said he is flying in the Caribbean. Don't think you need pitot heat there in a C 152. 

 

 

 

2 minutes ago, Bobsk8 said:

OP said he is flying in the Caribbean. Don't think you need pitot heat there in a C 152. 

 

Then he probably got a wasp in the pitot tube because he didn't cover it 😄

https://avherald.com/h?article=50af272c&opt=0

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

Just did a circuit at Bora Bora. 29 knot wind.  No air speed active. Not circuit breaker problem, not Pitot cover left on. Alternator light on dash doesn't seem to respond to low rpm's either. I'm pretty sure it didn't use to work like that.  Using the beta.

Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's

15 minutes ago, jimcarrel said:

Just did a circuit at Bora Bora. 29 knot wind.  No air speed active. Not circuit breaker problem, not Pitot cover left on. Alternator light on dash doesn't seem to respond to low rpm's either. I'm pretty sure it didn't use to work like that.  Using the beta.

Beta? What beta? 

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

8 minutes ago, Alvega said:

Beta? What beta? 

AAU02

Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's

1 minute ago, jimcarrel said:

AAU02

Oh, AAU2 is not beta anymore. You say no pitot cover left on during flight, but did you put in on when you finished last flight or left it without the cover?

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

I guess there are hundreds of aircraft across the country that are going to take off with no airspeed indication because of pitot tubes blocked by bugs 🙄

My flight school didn't use pitot covers on any of the rentals. Not saying they aren't a good idea, just saying it isn't particularly realistic if leaving the cover off between sessions automatically causes the pitot tube to get blocked, especially since there is no way in the sim to actually check/clear a block during a walk around.

7 minutes ago, Funky D said:

I guess there are hundreds of aircraft across the country that are going to take off with no airspeed indication because of pitot tubes blocked by bugs 🙄

My flight school didn't use pitot covers on any of the rentals. Not saying they aren't a good idea, just saying it isn't particularly realistic if leaving the cover off between sessions automatically causes the pitot tube to get blocked, especially since there is no way in the sim to actually check/clear a block during a walk around.

It doesn't automatically causes it to get blocked, but there is a chance that happens, like IRL.

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

3 hours ago, jimcarrel said:

Just did a circuit at Bora Bora. 29 knot wind.  No air speed active. Not circuit breaker problem, not Pitot cover left on. Alternator light on dash doesn't seem to respond to low rpm's either. I'm pretty sure it didn't use to work like that.  Using the beta.

Found this message the dev posted on Discord last month about the light:

Quote

It’s actually an “over-voltage” light per the POH, something not done in the sim, and would be hard to replicate given how locked down the electrical system is.

So for this plane, it’s been “re-wired” to act as a battery low voltage light, as a warning that the battery is probably not being charged by the alternator.

According to the dev the light should turn on when the battery charge is under 24.5v.

Edited by Alvega

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.