Rainmaker

I'll be the first to ask a stupid question. Is that white mounting board for the keypad buttons something that was bought from somewhere, or is that part of the print files? I just ask it was obviously a different color and looks like you have more than one of them in the picture.

Different fuel weight, CG location, etc. its all dynamic. And you have a 40K airplane and two tires, if you think you are just going to stop in those cases well then…. Anti skid is inoperative below about 15 knots. Doesn't exist.

Over-G damage most likely. The resolution is to not due things that cause aiframe damage.

Its the same as I just noted above. A tire does not have to be 'locked up' in order to skid. A skid is the tire being slow enough to cause a loss of friction. IE the wheel just moving too slow. It does not have to lock up to do that. No different than the opposite and stepping on the gas in a car and breaking traction the opposite way.

That's not what a skid is. A skid is wheel speed vs overall velocity. The two are not necessarily the same thing. You are looking for the wrong things to make that determination.

Zero things perceptively wrong in your track. You are in a skid. The resolution to that is not standing on the brakes at low speed.

Not really. FWIW, that is a C model thing. They do not have hand pumps to move the canopy. Its a pro move to start the engine to have hydro for the canopy so you can pull the strut. Not gonna really see that done on Es. Canopy is typically gonna be lowered after second engine start unless there is foul weather going on where you may want to shut it earlier.

The same as already said earlier. The one that matters is the Util press. Right side = 2750. Left = 3000 PC1 and PC2 are 3K regardless

Checklist is wrong EMD and hydro are not even related

It becomes a factor when 0 - negative Gs are held past a certain time. IRL, it's never a guarantee that it would happen. In DCS, it limits people from doing a bunch of silly things.

Why would you test? It's intentionally modeled that way.

Correct

Or a separate set nav function, like MN in this case, so you dont necessarily worry about trashing the INS. cant imagine that would be an enjoyable event.

I tested #1 about 2 weeks ago. It was right around 2600#:min. For #2, have never seen this bug at any time. If its happening for you, you need to provide a track #3. Dont look for that to be altered any time soon. Aircraft performs very well vs the data available. Thanks

This has been discussed before. I dont know why ‘commercial’ aircraft are being brought into the discussion here. The drift rate quality number is not an absolute, as it was commented above before, and just as you restated in your post. The numbers are not absolute, and the jet does not give you absolutes in terms of a defined drift over time. So, what I was commenting on is the time = x distance comment. The drift error is not near as simple as it was being made to be. You cant just solve the math by going X time equals X distance in error away from the original location. Everything you pretty much put in your post, is why I commented that the system does not work in the fashion that was posted in the original post. Beyond that point but also of note, the INS and EGI systems are separate. They are not inclusive as the other post suggested they were. Edit: I do see that part of your post may have been directed more at SD than at my post. The lack of quotes just muddied the water a little bit.

Thats not how drift really works. In addition, the drift rates are not that much.

You essentially start the mission with 30 minutes of drift already in place. Really only effective if you are starting missions in flight, which is what it was designed for.

INS is still its own system. But, yes, since EGI is there, you wont really notice unless you select it.

1. As above 2. Its used to set the accuracy of starting PP coords when you enter the jet. Unselected, coords will be accurate. Can still be flown with either alignment method, but there will be pos errors if full alignment in not completed 3. Is predetermined INS drift. Used to add drift error at mission start. 4. Old. Will probably eventually get removed or repurposed. Serves no function currently.

Your data is no longer accurate….

Would bet you are likely stalling the wings, which has less to do with any sort of ‘issue’ and more to do with flying technique.

Already exists. Has since day 1.

That’s incorrect. It is not supposed to release and doesnt.

No. That’s not how that works.

Or thats a sign of poor tactics on the part of the E model flyers…not sorting radar scans between them so the tactic is negated.