United Virtual Airlines

The January schedule has been uploaded to the servers and is now in effect. The searchable Excel file will be loaded to the VHQCC - Downloads page shortly.

Per normal policy, the reservations that have not yet been completed have been deleted. Pilots flying those flights should re-reserve the flight and then file the PIREP.

Apologies for the late upload this month. We have a few new destinations (both domestic and international) in the January schedule, see if you can spot them.

It's time to fly!

KIAD-OTBD is a new one

Quite a few new hops in the schedule.
Just as an FYI, the 767-200 ER was retired from the UAL fleet. When we reserve a 767 flight, it should read 767-300ER. Not trying to nitpick, just a heads-up.

Jason is correct, UAL no longer operates the B767-200. However a few of our Star Alliance partners still flies them. In this month's schedule you will see code share flights UA4767 and UA4768 operated by LOT using B767-200ER. For UVA's simulation, we can use a B767-300 instead for the flight.

Nice job. KIAD-OTBD is indeed newly added in order to reflect real world UA codeshare operations.

There are quite a few other new flights...

My main point is that I have run into this problem even on some of the main UAL flights. A good example is UAL flight 937 from Zurch to Washington Dulles. This route is flown using the 763 but the current reservation center shows it as a 767-200ER. This is a mainline flight. I know for a fact there was at least 1 763 available in Zurich. With this new coding, it says there are no 767's available. I think the problem is the aircraft identifier. It shows as '767' instead of 763. The same thing seems to be happening with the 777 routes. Instead of showing '777', it shows '772' and shows no planes available.

Dont quote me on this new destination... but is VOBG, HAL Bangalore International Airport, India one?

Ok, looks like what we have is an aircraft ID problem.
If you log into the pilot center, then go to the flight schedule page and select the ORD-DEN flight. It lists several available flights using the 767. As I mentioned before, UAL retired the 767-200 a few years ago and no longer has it in the fleet.
Let's look at an example:
Flight 259 is a flight from ORD to DEN using the 767-300 and shows '763' as the plane's identifier. If you click on the flight number like you're going to reserve it, it shows 2 767-300's available.
Now go to flight 245. This is also a flight from ORD to DEN using the 767-300. In the aircraft identifier, it says '767'. If I click on that number, it shows no 767's available and shows them as 767-300ER.

The same conflict exists with the 777's identifier.

If I want to reserve flight 926 to EDDF from SFO, it lists '777' as the aircraft identifier and shows 7 of them available in SFO for that route.

Now if I want to fly to Honolulu on flight 73, it shows '772' under the aircraft identifier and shows nothing available.

I understand that the identifers like 744M, 772, 767, etc all are used for codeshare flights. The issue is the mainline flights. As I said earlier, this is not to nitpick but it is something we should address. Thanks in advance.

I get what Jason is saying. I just flew a 777 RJAA-KSFO and now want to fly FLT 52 KSFO-KORD which is listed to be flown by a 772. However our planes are listed as 777's so I can't fly the flight because it's looking for a 772 when our's are listed as 777's.

It looks like the schedule database that was uploaded didn't have the manual corrections we do to make all 777 flights tied to the 777 a/c code and all mainline UAL 767 flights tied to the 763 a/c code. We'll get it fixed.

Dave

Thanks gents for pointing out the problem. All B763 and B777 flights are now fixed in the database.

Enjoy the friendly skies!

Somebody has to go around and clean up all your "droppings" j/k