• Content count

  • Joined

  • Last visited

Community Reputation

46 Excellent


  1. AirTran XM Radio

    Attached. README.txt
  2. AirTran dirty

    Version 1.0.0


    Dirty version of the AirTran Tan and Green livery. Currently operates for Delta Air Lines Fleet# 9541
  3. Simultaneous engine start

    It wouldn't be realistic since the pressure in the ducting would all drop unless the ISOL valve were closed and the right side were engaged. However, it looks like there is already logic in place when it comes to having both packs running and trying to start a single engine. The engine doesn't increase N2 and you get the START AIR LO message. Could this be coded in the same manner as trying to start both engines at the same time? If one starter is engaged and the other is then selected, it could behave this way too. Pressure drops low, none or little N2 movement and the message appears. Basically what Tango777 suggested. Also, for the normal way, have the PM drop about 3-8psi (good round number) when the starter engages and the engine rotates.
  4. Simultaneous engine start

    I really don't have enough info for this because it's not a normal practice to start both engines simultaneously. I can tell you what could happen by logic and design though. One thing I noticed in the sim, is that there is no drop in manifold pressure when you select one engine to start. The APU will throw all the air it can in a MES (main engine start) by opening the bleed valve all the way. But there will be a significant drop in pressure during start regardless. Minimum start pressure is 35psi. Given that, in RW, with both starters engaged the PM could drop below 25psi, which would trigger a START AIR LO alert. The engines would never make max N2 motor, and if the fuel switch was thrown (and the EEC allowed fuel to enter, min. N2 is 19 or 20%) it could lead to a hot or hung start. And the APU EGT could increase to the point that if it overtemped, it would close the bleed air valve and stopping any engine start altogether. That's just a few things that could happen but there's possibly more.
  5. Low Airspeed Protection wrong

    I have Vmin -5 and Vmin -10 with an engine out at cruise. What it's doing right now is low speed protection kicks in immediately when it touches the yellow band (Vmin) so it should allow some exposure below the minimum speed before it activates. The system description: These are out of the AOM: (Colored in for emphasis) Hope this helps.
  6. Airport filter

    Undoubtedly it's that. But I think his question was for a specific value/requirement to code it properly.
  7. Airport filter

    I don't think I have anything that specific about the software database. Going by memory that when pressing the airport select you wouldn't see farmer airports and uncontrolled, etc. But I can check later.
  8. Airport filter

    I think they had a software limitation where it wouldn't show airports with runways less than 5000' or not suited for 717 ops.
  9. Autoland off centre

    Tried to send it to you via messages, but it says you don't receive them.
  10. Autoland off centre

    It should be covered under radio altimeters. If you get around to it later and need some more info, let me know.
  11. Autoland off centre

    A better autoland capture. Difference is in last video, VApp was 157, Vref was 145 (forgot to reset, whoops), GW was 113.0 (not 130 which is impossible since max tarmac weight is 120), and runway was KMCO 35R. This video Vref is 145 set with FMS, GW is 105.0 and KMCO 35L (CAT III). As it shows, everything looks good, until flare and the aircraft floats and shortly climbs before settling and is off to the left. One other thing of note, is there is no rising runway popping up from the lower part of the PFD.
  12. Autoland off centre

    Granted this setup is out of limits, the point of the video was to demonstrate the aircraft ends up chasing the glideslope bar and reacts slowly to the change as well as to one side of the runway. This has occurred on a number of Autoland attempts with longer approaches, having landing weight within limits and VREF set accordingly. This weather setup was also set to standard temp, press, no wind and the Terrain callout was overridden because it came on erroneously on the last approach.
  13. Autoland off centre

    Yup. But I let it go this time to demonstrate. This happens about 1 out of 2 Autoland approaches.
  14. Autoland off centre

    It porpoised on final for me too and landed pretty long. This was actually the second approach. I did a planned go around earlier and came back, but then it got a bit wonky in the end.
  15. Autopilot becomes too aggressive when on an intercept course to the FMS flightpath. It should go to NAV ARMED when outside 10nm from the flight path and then when it captures, it should remain on heading or into the path rather than abruptly swing hard to the left or right (depending on the direction you're coming from). I've added a video to show exactly what it does for me when I select NAV while on and intercept course and then again while flying away. When flying away the FMC should tell me I'm not on an intercept course and should ignore the command to NAV instead of trying to steer to it. At 00:13 will be the on intercept capture. 4:22 will be the away from capture. 5:06 will be the direct intercept capture Creating this to follow another post i made awhile ago.