One future suggestion I would have for future releases:A not-so-perfect copilot. I know when I'm flying real-world, I've got to double-check everything the copilot does, making sure that all switches and checklist items are exactly where he says they are. I think that would add immensely to the program if there was a random variable for some items, ie., the copilot says he's got the flaps set to 5 for takeoff, but when you look, they're only at 1. I've caught a couple of copilots, who've gone through checklist items so fast, they miss or actually state things that aren't there. One time I had a copilot say "Landing gear, down, and locked", yet when I looked, one still said it was in transit. It happens, you get conditioned to checklists and you give out conditioned responses, I did it when I was a copilot. So, maybe just an idea that I'd have to double-check things a little more than I do now, remember even though the copilot may be responsible for a checklist item, as the Pilot-in-command, you're still responsible they get done.Don't know how hard it would be to code that in, but it would be interesting, especially since "Jim" seems to tell me I'm doing things wrong, I'd like to get him back. :-)

Hello Joe,I agree, the crew interaction in FS2Crew is almost too perfect and once you get the hang of FS2Crew, things go almost "too smoothly."It wouldn't be too difficult to code in what you're suggesting, but the problem is I'll get a lot of Support emails from people saying FS2Crew doesn't work properly because the FO is not doing his job properly.It could cause a lot of confusion.Cheers,Bryan

The would be the user-end problem under RTFM department.

I would think that if you put this as an option, with the default to "no mistakes", that you would avoid confusion. Just an idea...Heath