Jump to content
View in the app

A better way to browse. Learn more.

POSCON

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.

Another Bug found?

Featured Replies

1942288731_Immagine2021-03-28011010.thumb.png.263124f56016769330bc7ccf1ac8b60c.png

Hello my friends from the community!

Tonight I wanted to give a try to the Beechcraft B1900D (Carenado, Xplane 11) and did a double sector.

I logged as UAL118 (I thought that UCA, CommutAir, was not in the database yet, but actually it was...) for the first flight, KALB-KLGA. Everything went smoothly.

For the second sector, I logged as UAL99 (after disconnecting and taking a 15 minutes break), but when I tried to get clearance, a message appeared telling me something like "server wasn't able to find relative flight plan for this callsign" (I was in the activation timeframe for that second flight plan I prefiled).

But after logging off and on again, the flight plan was found by the server and I was assigned to the right sqwack code, and the flight showed correctly on the map.

 

Now, I came back 1 hour after the sector was over to check the stats for my flights...just to find out the 2 sectors were merged into one and it was as UAL99.

UAL118 doesn't even appear as callsign in the log.

I actually had some problems before with filing 2 flight plans for consecutive flights (with a distance of 45 minutes between wheels on dest. airport sector 1 and departure time from airport for sector 2 with different callsign). But this is an unique kind of bug, I guess.

I'm just reporting this bug. And a suggestion: Improve the possibility to file 2 flight plans (that have different departure times OFC), so a bug like this will never occur again. Or like the other one (which was related to the callsign used in those 2 flights being the same callsign, I guess).

 

893015665_Immagine2021-03-28011241.thumb.png.5fc0e38a4566add32ccd3c6b9d8979b8.png

Thanks for the attention,

I'm proud to support Poscon and help its improvement.

 

P.S: It's just my opinion, but the lenght of the flight in the graph should be shown as Nautical Miles, not Statute Miles.

  • Network Directors

First a point of clarification, because it is to me very confusing. When you refer to "sectors" you should be using the terms "legs" or "flight segments"

Anyway, when you connected to the network, in the connection window where it asks you to specify your ADS-B callsign - did you change this between flights, or leave it the same for both?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and Guidelines.

Account

Navigation

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.