Jump to content

Search the Community

Showing results for tags 'operational'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Network Forums
    • General Discussion
    • Feature Requests
    • The Everyday Aviation FAQ
  • Brazil Division's General Discussion
  • Turkey Division's General Discussion
  • France Division's General Discussion
  • Armenia Division's General Discussion
  • United States Division's General Discussion
  • United Kingdom Division's General Discussion
  • India Division's General Discussion
  • Argentina Division's General Discussion
  • Canada Division's General Discussion
  • Germany Division's General Discussion
  • Austria Division's General Discussion
  • Hong Kong Division's General Discussion
  • Ireland Division's General Discussion
  • Poland Division's General Discussion
  • Jordan Division's General Discussion
  • New Zealand Division's General Discussion
  • Morocco Division's General Discussion
  • Belgium & Luxembourg Division's General Discussion
  • Netherlands Division's General Discussion
  • Australia Division's General Discussion
  • Military Division's General Discussion
  • Colombia Division's General Discussion
  • Sweden Division's General Discussion
  • Bahrain & Qatar Division's General Discussion
  • Estonia Division's General Discussion
  • Georgia Division's General Discussion
  • Saudi Arabia Division's General Discussion
  • Greece Division's General Discussion
  • Italy Division's General Discussion
  • China Division's General Discussion
  • Japan Division's General Discussion
  • United Arab Emirates Division's General Discussion
  • Malaysia Division's General Discussion
  • South Africa Division's General Discussion
  • Israel Division's General Discussion
  • Kenya Division's General Discussion
  • Oman (Muscat) Division's General Discussion
  • Norway Division's General Discussion
  • Thailand Division's General Discussion
  • Spain Division's General Discussion
  • Latvia Division's General Discussion
  • Vietnam Division's General Discussion
  • Switzerland Division's General Discussion
  • Serbia & Montenegro's General Discussion
  • Korea Division's General Discussion
  • Singapore Division's General Discussion
  • Moldova Division's General Discussion
  • Venezuela Division's General Discussion
  • Iran Division's General Discussion
  • Egypt Division's General Discussion
  • Dominican Republic Division's General Discussion
  • Jamaica Division's General Discussion
  • Portugal Division's General Discussion
  • Denmark Division's General Discussion
  • Trinidad & Tobago Division's General Discussion
  • Slovenia Division's General Discussion
  • Russia Division's General Discussion
  • Finland Division's General Discussion
  • Taiwan Division's General Discussion
  • Pakistan Division's General Discussion
  • Hungary Division's General Discussion
  • Indonesia Division's General Discussion
  • Chile Division's General Discussion
  • Bahamas Division's General Discussion
  • Kuwait Division's General Discussion
  • Lebanon Division's General Discussion
  • Romania Division's General Discussion
  • Algeria Division's General Discussion
  • Slovakia Division's General Discussion
  • Philippines Division's General Discussion
  • Sri Lanka Division's General Discussion
  • Ukraine Division's General Discussion
  • Croatia Division's General Discussion
  • Bulgaria Division's General Discussion
  • Iceland Division's General Discussion
  • Tunisia Division's General Discussion

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


First Name


Last Name


Company Name


User ID


Discord ID

Found 2 results

  1. Have you ever approached an airport too high or too fast and as a result you had to dive bomb the runway in order to land? Have you ever landed halfway down the runway in an attempt to squeak out that perfect landing rate? If the answer is yes to either of these questions, then you are the victim of an unstablized approach and in the POSCON world, you lose points for that type of flying. One of the biggest operational challenges for a virtual pilot is how to successfully accomplish a stabilized approach in the simulator. In fact, flying stabilized approaches in the flight simulator is difficult for even the most experienced real world pilots because of the inherent limitations of flight simulators such the limited FOV (field of view) compared to the real world. In this post, I am going to attempt to tackle the reasons why stabilized approaches are such a challenge and offer some techniques on how to ensure your approaches remain stabilized. For our example scenarios, we are going to John Wayne - Orange County Airport located in Santa Ana, California (KSNA). This airport has two parallel runways: Runway 20R/2L - this is the larger of the two runways at 5,701 x 150 feet with all of it available for landing. Runway 20L/2R - this is the smaller of the two runways at 2,887 x 75 feet with all of it available for landing. Runways 20L and 20R from X-Plane 11: This is an old real world photo when the runways were previously named 19L and 19R. Not sure if you noticed, but there are two very important differences between the two photos other than the runway naming. The first difference is that in the X-Plane photo, the runway touchdown zone markings extend the entire length of the runway which gives the flight simulator pilot a false sense of where the touchdown zone is located. In the real world photo, there are only three touchdown zone markings (not including the threshold markings). Each touchdown zone marking indicates 500 feet. You might ask, why are there only three in the real world? For that, lets define the term "touchdown zone". Touchdown zone = the first 3,000 feet of a runway or first third, whichever is less. In the case of KSNA, that means the touchdown zone is defined as the first 1,900 feet (5,701 divided by 3). So at KSNA, the runway painters only painted 3 markings to indicate the touchdown zone (3 x 500 = 1,500). Anything more than that would give the pilot incorrect information. The second major difference between the two photos is the fact that the X-Plane runway is simply too long. You can tell this because of the location of the third touchdown zone marking in relation to the taxiway. In the real world photo, the taxiway is located in the same position as the third marking, but in the X-Plane photo, the taxiway is located in the same position as the fourth marking. These types of scenery inaccuracies present a significant challenge to flight simulator pilots because landing in the touchdown zone is a requirement of every landing and the expected outcome of flying a stabilized approach. If you estimate that you will NOT land in the touchdown zone, a go-around MUST be initiated. POSCON will automatically deduct points from your score if you fail to land within the touchdown zone because it is indicative of an unsafe landing. We now know what the touchdown zone is and why it is important, but to achieve a safe landing in the touchdown zone, it first starts with a stabilized approach. Significant speed and configuration changes during an approach can complicate aircraft control, increase the difficulty of evaluating an approach as it progresses, and complicate the decision at the decision point (i.e., DA, DDA, DH, MDA). Assess the probable success of an approach before reaching the decision point by determining the requirements for a stabilized approach have been met and maintained. Normal bracketing is defined as small corrections in airspeed, rates of descent, and variations from lateral and vertical path. Normal bracketing is a part of any instrument or visual approach procedure. Frequent or sustained variations are not normal bracketing excursions and are not acceptable. POSCON will automatically deduct points from your score if you fail to conduct a stabilized approach; however, you will only be charged points if the approach results in a landing. If you realize you are unstable and go-around without touching down, no points will be deducted. Let's review the criteria the POSCON grades on: Stabilized Approach Requirements On any approach, the following is required: Below 2,000 feet above field level, do not descend at a rate greater than 2,000 FPM for more than a few seconds. Below 1,000 feet above field level, or inside the FAF, do not descend at a rate greater than 1,000 FPM for more than a few seconds. EXCEPTION: At special airports such as Lukla (VNLK), Telluride (KTEX), Aspen (KASE), Paro Bhutan (VQPR), etc. OR if you are simulating an emergency, you can "dispute" the point deduction in order to be exempt from the above criteria. We also are considering exempting certain aircraft types as well such as general aviation. At 1,000 feet above field level: You must be in a landing configuration (gear down and final landing flaps), no exceptions. On the proper flight path. At stabilized thrust (spooled). Minimum speed: target speed minus 5 knots. Maximum speed: target speed plus 10 knots. EXCEPTION: In VMC, the requirements at 1,000 feet can be delayed until 500 feet above field elevation, except landing configuration. These requirements must be maintained throughout the rest of the approach for it to be considered a stabilized approach. If the stabilized approach requirements cannot be satisfied by the minimum stabilized approach heights or maintained throughout the rest of the approach, then you must execute a go-around. The decision to go around is not an indication of poor performance, but rather good judgement. Main Causes of Unstabilized Approaches Visual approaches. Poor descent and speed planning from cruise. Unreasonable ATC speed or altitude restrictions. Techniques to Flying a Stabilized Approach Here are some tips on how to achieve a stabilized approach: Stabilized approaches start with good descent and speed planning. The total flying distance required for a normal descent to landing can be calculated by factoring 3 miles per 1,000 feet or 1 mile per 300 feet (3 to 1 ratio). Sometimes, however, a 3 to 1 ratio cannot be maintained due to high tailwinds, engine anti-ice activation, or ATC assigned speed restrictions. If you are flying jet aircraft, make sure you are not afraid to use speed brakes when necessary as they are a very effective tool to "go down and slow down" simultaneously. If you are in variable pitch prop aircraft, you can push the prop lever full forward which will use the blade of the prop to help slow the aircraft. The best way to slow an aircraft in the descent is to level. It is not always possible, but when it is, it is good practice to build in a few extra miles prior to a speed restriction to level just to make sure you can achieve the desired speed. If the act of leveling gets you off your desired descent path (i.e. too high), you can always add flaps to maintain a high descent rate while maintaining a slow speed. Speed brakes can also help, but avoid using speed brakes below 180 KIAS. Extending your gear is your trump card... play it when necessary. The gear is the biggest drag device you have on your aircraft. If the choice is between going around and dumping the gear early, the gear is always the best option. 1,000 feet is just a minimum. You should target 1,500 feet to ensure you are stable by 1,000 feet. In general, plan to be stabilized on all approaches by 1,000 feet above field level in both IMC and VMC. Use electronic guidance when available. This does NOT mean you need to request to fly the instrument approach, you can simply tune and backup your visual approach using an ILS or RNAV for the vertical guidance that these approaches provide. A good technique on visual approaches is to intercept the vertical path, even if not established on the lateral guidance. If ATC assigns you an altitude or speed restriction you are unable to maintain, then simply say "unable". Know how to properly manipulate the the mode control panel (MCP) or guidance panel (GP) on your aircraft. Knowing what the different modes do will help you make good decisions during the descent phase. Also, it is important to understand how each mode interacts with your auto-throttle system. The last thing you want is the auto-throttles to increase power when you are not ready for them to do so. Here is an example of what to do when you recognize early that a 3 to 1 ratio descent path is not going to work: Okay, now lets say you have tried ALL of the above and you are out of options, what now? Do you have to go-around? There is one more option... increase the flying distance to the runway. You can do this a number of different ways, but it depends on how far away you are from the runway. Early recognition of being unstable: If you realize early that you are going too high and/or fast on approach, you can ask ATC for "vectors for descent". 99% of the time ATC will be happy to accommodate this request because they rather give you a chance to make a stabilized approach than have to deal with your go-around. Late recognition of being unstable: If you realize that you are going to be high and/or fast and you are on final approach, then things become a little bit more complicated. With the exception of the C172-type aircraft and their ability to forward slip, the only option is an S-turn... yeah, that thing from the private pilot training. If you are flying into a controlled airfield, you need to request to conduct this maneuver from ATC. If you are flying into an uncontrolled field, you can simply perform this maneuver on your own. CAUTION: Some people may suggest a 360 degree turn for stabilization on final as it is common practice at uncontrolled fields. I personally do not recommend this maneuver as it can lead to bad things if aircraft are behind you. If you feel that the S-turn technique will not work, it is better to just level at pattern altitude, fly upwind and then re-enter the traffic pattern. The S-Turn Technique The shortest distance between two points is a straight line, thus if you want to increase the distance to a runway (i.e. the time to descend and slow), you need to add a bend in your flight path. In order to do this, first make sure you are above 1,000 feet above field level and in VMC. If not, you need to go around and try the approach again. If you are, I recommend the following technique: Turn 30-45 degrees off course. Maintain throttles to idle. If you are too high: pitch for maximum vertical descent rate based on height above field level (e.g. do not exceed 2,000 FPM below 2,000 feet AFL or 1,000 FPM below 1,000 AFL). If you are too fast: pitch for desired airspeed. Evaluate your glide path using visual or electronic means. When you feel comfortable with the stability of your approach, turn back towards the airfield and intercept the straight-in final. CAUTION: Do not let the maneuver deviate more than 1 mile from the straight-in lateral track, otherwise you might as well go around and re-enter the pattern.
  2. You're flying along from Miami to Chicago talking to various air traffic control centers while en route. About halfway to Chicago, you notice radio silence; you try calling air traffic control with no answer. You check your microphone settings, everything seems to be working normal. What do you do? Another day, you're flying a Cessna 172 VFR in your local practice area without talking to air traffic control when all of the sudden you notice black smoke coming out of the engine. You see an airport in the distance and you head towards it but you have no idea what airport this is. You need assistance from air traffic control, but have no time to figure out the proper frequency to contact, obviously, you are handling an emergency. What do you do? In both of these scenarios, GUARD frequency (VHF 121.5 and UHF 243.0) can be an effective tool. This is a frequency reserved for emergency transmissions as well as for aircraft that have missed a check in with ATC or not sure what frequency they should be on. 121.5 is used all over the world and nearby air traffic controllers are always monitoring this frequency. In the first example we described, you could switch to 121.5 and transmit: "Delta 123, on GUARD, I lost contact with Memphis Center, can someone advise which frequency I should be on?" On the reverse side of things, air traffic controllers can use GUARD to locate an aircraft they were expecting to hear from or that have not been responding. For example, an air traffic controller could say: "American 123, Memphis Center, on GUARD, if you hear this message, switch to my frequency on 132.4." Sometimes an aircraft may be unresponsive because they are out of range of an air traffic controller's radio transmitter. Since there are often aircraft positioned in different parts of a center controller's airspace, a controller may ask another pilot for assistance to relay a message on GUARD in the hopes that their location will transmit a better signal to the unresponsive aircraft. In this scenario, GUARD provides an excellent resource in ensuring all aircraft are accounted for. In the second example, we see the potential use of GUARD in an emergency scenario. The pilot could switch to GUARD and state that they have an emergency and are landing at the nearest airport. Since all air traffic controllers monitor GUARD, a radar controller can transmit on GUARD and provide better assistance to the pilot by issuing radar vectors, recording important information pertaining to the emergency, and coordinate for crash fire and rescue to be ready at the diversion airport. Interesting to know as well, when an ELT beacon goes off, it transmits an aural signal on the GUARD frequency. Organizations like the Civil Air Patrol actually practice triangulating and locating a beacon to find the location to prepare for search and rescue missions in the event an aircraft crashes. The beacon signal from ELTs almost sounds like a siren. One final example worth mentioning is the DOD (e.g. Air Force, Coast Guard) monitor GUARD as well. Aircraft crossing over our international borders without following proper ADIZ entry procedures can be intercepted by military aircraft who will use GUARD frequency in an attempt to establish communication with the violator. If two-way communication is established on GUARD, the intercepting aircraft can provide further instructions to the pilot as necessary. In conclusion it is strongly recommended, and in most instances required, for pilots to always monitor GUARD 121.5 on their second radio. In fact, airlines require crews to monitor 121.5 on a second radio when the radio is not needed for other operational reasons. Monitoring GUARD provides an extra layer of safety and if you accidentally transmit on GUARD, don't worry, there are plenty of pilots that will key up in a funny voice to remind you "You're on GUARD"... hopefully that doesn't happen during a time when you really need it. On POSCON, we simulate the GUARD frequency on both VHF and UHF frequencies to provide an ultimate realistic experience. Next time you find yourself on the network in one of these scenarios, try the GUARD frequency. For more information, check out the AIM 6-3-1.
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and Guidelines.