787WannabePilot

Very cool.

I flew a B7378 into Fort Myers a few weeks ago. That pilot rode the speed brakes hard.

I had no idea you could do this... thanks!!

http://www.huffingtonpost.com/entry/how-to-land-a-737_us_56c13aebe4b0c3c55051d43b Looks like it.

Cool. And thanks.

Every flight I have taken out of the NYC area has done a "cut back" after take off. First time I flew, I thought the engines were shutting down on me.

Second, pan up and turn on the battery.. does that turn the instruments on? (I am taking a shot in the dark)

I used PFPX. Thanks for the rest of the information.

Thanks.. that is what I have been doing.

Was planning a flight from KRSW to MWCR. I auto planned the route, coming up with CSHEL5 LAL DCT RSW DCT TADPO UG448 ATUVI GORAN3. The SID was CSHEL5 and the TRANS used was LAL. Following this departure route, it increased the overall length by 50%. Further, the LAL to TADPO was a 180 degree turn. In scenarios such as this, would a SID even be used? Would their be modification to make it more efficient in both distance and turns?

Passing the DECEL will automatically move the speed to the "UP" section of the speed tape. Once I get there, I extend flaps one. However, by the time I am turning to the localizer for the approach, I am not at flaps 5, as the aircraft hadn't slown down enough.

I meant "DECEL", it shows on the map with all the other waypoints along the flight path.

I am attempting to follow this approach chart; http://www.arianedesign.com/modules/assets/master/upload19069-577_XBoeing737NORMALPROCEDURES.jpg It shows the airplane in flaps 5 prior to the final approach. However, when flying in the sim, the "DECEL" point is too close to the final approach to meet the speed requirement. If put the flaps down sooner than the DECEL point, the FMC locks on VNAV speed, messing up the flight path. (Come in way to high for the approach) Other than using the speed brakes once crossing the DECEL point (which sometimes isn't even enough), what else can I do? Is flaps 5 not supposed to be reached prior to the approach leg / VOR is captured? Thanks.

PMDG hasn't released their compatibility download yet, so, I am not quite sure how you guys are getting it to work with V3.

For those wondering about VAS; (taken from the PMDG side of avsim) "2) VAS VAS VAS VAS VAS: Our testing internally leads us to conclude that Lockheed Martin's development team has succesfully updated Prepar3D so that it will unload data that is no longer needed in memory. More specifically, our testing seems to conclude that data accumulation in VAS related to scenery being seen or over-flown is no longer a factor for simmers using Prepar3D. I want to stress that our testing was done in-house, and was not scientific- but we know very well how to replicate OOM issues with Prepar3D and FSX, and running those same tests with Prepar3D v3 yielded far lower VAS volumes than we have ever seen, even when moving between very intense scenery areas."