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.

737 training touch and go--must see

Featured Replies

The video is called: 737 cockpit video - takeoff and landing practicePilot in training performing touch and go's. Good practice/exercise for those of us flying the 737. Helps to better understand how to do these touch and go's. Sidenote: having difficulties with the FMC while setting it up for an ILS approach to an airport I have just taken off from. Usually when coming in for a landing and setting up the FMC for a ILS approach-->the legs page will show the altitude to be at for each waypoint of the ILS. It doesn't matter what I do (deleting and re-inputting the arrival airport, deleting the runway for that airport I have just taken off from) the altitudes for the waypoints no longer show up and/or the waypoints sometimes do not show up at all. All this said after setting up the FMC for an ILS approach with the missing information the aircraft will still pick up the ILS and it will autoland if I want--it would just be nice to see those waypoints or the altitudes for them. FLight charts are great to use to get this info but I was just curious as to what I am doing wrong with the FMC to not get this information on the legs page.Thanks,Chris

I can't tell from the description if you are missing the constraints that should be entered from the sidstar file of if you are missing altitudes generated by the FMS VNAV path predictor.Try putting in a nearby VOR with at your cruising altitude then select the approach (and transition if any) after the VOR, once set up you can always direct to the FAF for the approach.

Dan Downs KCRP

  • Author
I can't tell from the description if you are missing the constraints that should be entered from the sidstar file of if you are missing altitudes generated by the FMS VNAV path predictor.Try putting in a nearby VOR with at your cruising altitude then select the approach (and transition if any) after the VOR, once set up you can always direct to the FAF for the approach.
Thanks, it was the later. Your suggestion worked.

Create an account or sign in to comment

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.