@Quasi_Stellar I’m willing to bet it’s Mean Sea Level, especially if it’s above the local transition altitude. In the KTO, it’s 14,000 ft., in the United States it’s 18,000 feet. While climbing out, when passing these altitudes, the altimeter should be set to 2992, the standard mean sea level pressure.

IIRC - most if not all of our fighter refuelings were performed in an orbit area, with all turns being to the left.

We’d orbit at the ARCP at best endurance (or thereabouts), then accelerate to 315 KIAS when a fighter flight rendezvoused with us. Our nav (we had them then) would make the conversion to KTAS.

@matini said in Will the KC-46 be incorporated into BMS?:

@JollyFE

I saved this picture and posted it on the FB interest group dedicated to boom operators. A lot of the members have gotten a kick out of it.

Just finished flying an escort mission for a TASMO strike. After landing, the mission result for my flight was mission failure - 0 losses to enemy air defenses.

Wait a cotton-pickin’ minute. None of the strike flight was lost to enemy fighters, primarily because none came up to play, and we got a failure?

@Ricky I think, in this case, AI stands for “Aerial Intercept.”

Note the type of aircraft at the bottom of the box in order to select the correct seat.

@Ricky I think, in this case, AI stands for “Aerial Intercept.”

Note the type of aircraft at the bottom of the box in order to select the correct seat.

@Quasi_Stellar I’m willing to bet it’s Mean Sea Level, especially if it’s above the local transition altitude. In the KTO, it’s 14,000 ft., in the United States it’s 18,000 feet. While climbing out, when passing these altitudes, the altimeter should be set to 2992, the standard mean sea level pressure.

Just finished flying an escort mission for a TASMO strike. After landing, the mission result for my flight was mission failure - 0 losses to enemy air defenses.

Wait a cotton-pickin’ minute. None of the strike flight was lost to enemy fighters, primarily because none came up to play, and we got a failure?

In every iteration of BMS that I’ve flown, the digital compass readout in the HUD has gone 358 . . . 359 . . . 000 . . . 001, etc .

I think it should be 358 . . . 359 . . . 360 . . . 001.

Consider this - the runways at Gunsan (Kunsan) are 36 and 18, not 00 and 18.

@Bayonet

Perhaps you could take the lead, and request refueling yourself. Instead of moving directly into the contact position, fly formation for a while in the position you just described.

It seems to me that the DED shows the planned TOS, whereas the HUD shows and updated time based on the actual GS.

@matini said in Will the KC-46 be incorporated into BMS?:

@JollyFE

I saved this picture and posted it on the FB interest group dedicated to boom operators. A lot of the members have gotten a kick out of it.

@Quasi_Stellar said in U1 update will not run:

@huffer2 extract the .exe somewhere. Then run the .exe, and when prompted, point at your setup folder and go from there

This is what I did, and had no problems installing the update.

@windnc60 said in A-G Mode -unable:

I would assume the Missile and Dogfight overrides are the culprit here. As I tried it this morning i brought it out of “override” and the RT MFD switched to A-G mode when I pressed the A-G button on the ICP. Go Figure, Many thanks to all.

That sounds reasonable. That’s why they’re called ‘override’ functions. I think it’s in the User Manual when crafting a TE that you set up your A-G parameters once airborne, then engage Missile Override until you reach the target IP.

IIRC - most if not all of our fighter refuelings were performed in an orbit area, with all turns being to the left.

We’d orbit at the ARCP at best endurance (or thereabouts), then accelerate to 315 KIAS when a fighter flight rendezvoused with us. Our nav (we had them then) would make the conversion to KTAS.