Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

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.

Great Addon - A Few Notes...

Featured Replies

Hello FS2Crew Team,

First of all, congratulations on yet another fantastic release.  My first experience with FS2Crew was back in FS2004 and the PMDG 737.  I was a young commercial pilot at the time and it certainly helped get me acclimated with the way things work in terms of flows/checklist on airliners.  I've since flew the real B737, so although I've haven't flown the A320, feel I could provide feedback on a few small items that I believe would be applicable to most any 121 operation. Although small, I believe these suggestions would help finish polishing an already fantastic (and must-have) addon.  These suggestions come from noticing certain procedure parallels between the carriers I've flown for over the years here in the US.  

1.  Flight control check + T/O announcement:  We normally do the flight control checks right after engine start and prior to taxi.  Currently the addon triggers the takeoff announcement after completing the flight control check, which in most cases is very early, especially when taxiing at larger airports.  May I recommend the trigger be when the "BEFORE TAKEOFF" checklist is called.  

2. Emergency exit lights: I've noticed they are switched off upon shutting the engines down.  In my experience, these should remain on during the entire deplaning process in case of an unexpected fire/smoke (from APU or elsewhere) where an emergency evacuation would need to be conducted.  My suggestion would be to include them to the securing aircraft flow.  

3. Wing lights: At least here in the US, most carriers have pilots leave these lights on at or below 18,000 FT (AGL) to maximize the visibility of aircraft, along with most all other lights.  I noticed they're currently being switched off shortly after takeoff.  While these lights are designed to detect icing on the wings, they're also a great proponent to safety, especially at night.  Some carriers make this optional if it's day, others have their pilots do it regardless of time of day.  

Finally, I have a question. What is the standard callout for when power is set and the ASSIST calls for <<ANNOUNCE FMA INDICATIONS>> (sp?) - ? Would be wonderful to have a "template" to follow.  

Thanks again for taking our sim experience up to new heights and I certainly look forward to your reply.  

Kind regards,

JD 

  • Commercial Member
8 minutes ago, JDSZ said:

Hello FS2Crew Team,

First of all, congratulations on yet another fantastic release.  My first experience with FS2Crew was back in FS2004 and the PMDG 737.  I was a young commercial pilot at the time and it certainly helped get me acclimated with the way things work in terms of flows/checklist on airliners.  I've since flew the real B737, so although I've haven't flown the A320, feel I could provide feedback on a few small items that I believe would be applicable to most any 121 operation. Although small, I believe these suggestions would help finish polishing an already fantastic (and must-have) addon.  These suggestions come from noticing certain procedure parallels between the carriers I've flown for over the years here in the US.  

1.  Flight control check + T/O announcement:  We normally do the flight control checks right after engine start and prior to taxi.  Currently the addon triggers the takeoff announcement after completing the flight control check, which in most cases is very early, especially when taxiing at larger airports.  May I recommend the trigger be when the "BEFORE TAKEOFF" checklist is called.  

2. Emergency exit lights: I've noticed they are switched off upon shutting the engines down.  In my experience, these should remain on during the entire deplaning process in case of an unexpected fire/smoke (from APU or elsewhere) where an emergency evacuation would need to be conducted.  My suggestion would be to include them to the securing aircraft flow.  

3. Wing lights: At least here in the US, most carriers have pilots leave these lights on at or below 18,000 FT (AGL) to maximize the visibility of aircraft, along with most all other lights.  I noticed they're currently being switched off shortly after takeoff.  While these lights are designed to detect icing on the wings, they're also a great proponent to safety, especially at night.  Some carriers make this optional if it's day, others have their pilots do it regardless of time of day.  

Finally, I have a question. What is the standard callout for when power is set and the ASSIST calls for <<ANNOUNCE FMA INDICATIONS>> (sp?) - ? Would be wonderful to have a "template" to follow.  

Thanks again for taking our sim experience up to new heights and I certainly look forward to your reply.  

Kind regards,

JD 

Hi JD,

Nice to talk to a long time user 🙂

Well, the Airbus is a very different than the Boeing as you know.

1. Airbus manual has the flight control check done during taxi, obviously to save time.  Blocking the taxiway doing a flight control check may not make people happy, either.

But in FS2Crew you could do the flight control check prior moving the plane if you wanted, at least in Voice Control.

2. Emergency Exit lights.  It may be a bug.  I'll have to double check.  They should go off during the Securing aircraft flow, not during the parking flow.

3. Lights:  That's an American thing, but we do have an option to set the lights at 18K on the Config screen for US guys.

4. Take off FMA... would be like "Max Flex 53, SRS Runway, Autothrust Blue".  Just basically read what you see.

 

Cheers,

  
 

 

 

  • Author
3 minutes ago, byork said:

Hi JD,

Nice to talk to a long time user 🙂

Well, the Airbus is a very different than the Boeing as you know.

1. Airbus manual has the flight control check done during taxi, obviously to save time.  Blocking the taxiway doing a flight control check may not make people happy, either.

But in FS2Crew you could do the flight control check prior moving the plane if you wanted, at least in Voice Control.

2. Emergency Exit lights.  It may be a bug.  I'll have to double check.  They should go off during the Securing aircraft flow, not during the parking flow.

3. Lights:  That's an American thing, but we do have an option to set the lights at 18K on the Config screen for US guys.

4. Take off FMA... would be like "Max Flex 53, SRS Runway, Autothrust Blue".  Just basically read what you see.

 

Cheers,

  
 

 

 

Thanks for the prompt reply, Bryan!

Ah, good to know the FLT CTL check is done during taxi on the A320, that certainly makes sense.  I assume we'd have to tempo disable nosewheel steering for the rudder check - or do you know what the procedure is? Fantastic to know you've made an option for lights at 18K!  Thank you very much for the FMA example. 

Keep up the great work!

JD

  • Commercial Member
30 minutes ago, JDSZ said:

Thanks for the prompt reply, Bryan!

Ah, good to know the FLT CTL check is done during taxi on the A320, that certainly makes sense.  I assume we'd have to tempo disable nosewheel steering for the rudder check - or do you know what the procedure is? Fantastic to know you've made an option for lights at 18K!  Thank you very much for the FMA example. 

Keep up the great work!

JD

On the tiller, there's a Disconnect switch you can push in to decouple the rudder from the nosewheel.

I don't think the FBW models that, though.

I actually recommend users just stop the plane when doing the flight controls check otherwise you can swerve around too easily.

 

Edited by byork

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

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.