Due to continued close calls during flight operations, the motorglider operating procedures have been updated to read:
Motor Glider Launches
Motor gliders under power should follow standard procedures for power traffic at MEV. Motor gliders launching from 34 should make a right turn after departing to avoid tow planes launching from 30, and to provide an easy right pattern for 30 in case of an engine failure. Note that caution is required if skydiving operations are active. If launching from 30, a standard left 270° turn should be made inside of the normal traffic pattern for 34.
Our goal is to avoid simultaneous motorglider take-offs on Runways 30 and 34. First, visually confirm that there are no traffic conflicts. We work to keep the foliage in the sightlines between the two runways clear, but it can be difficult to spot motor gliders on the other runway. Second, use radio transmissions to help avoid traffic conflicts. We try to keep powerful radios available for the crew chief in the staging area, hand-helds for the flight line team, and the towplane can assist when on the ground. The recommended radio procedures are as follows:
Self-launch gliders using runway 34 should
- Request a radio-check before taxiing far down the south end of the airport, where it is harder to hear weak radios
- Make a transmission shortly before taxiing on to the runway, e.g. “Glider EE about to taxi onto 34 for immediate departure”. This gives the Glider Line Chief a chance to warn runway 34 traffic about a 30 departure before they are on the runway.
- Assuming no conflicts, make the usual call announcing take-off (“Glider EE take-off runway 34”)
Self-launch gliders using runway 30 should
- Request a radio check from the Line Chief at least a minute before take-off, and if no response is received, talk to the line staff about the problem
- Make an announcement one minute before take-off (e.g. “Glider 1C ready for departure in one minute” and then listen attentively for a response from the Line Chief, who can use this minute to verify no one is using 34, and call for the 30 glider to wait if, for example, an Archer is ready to depart 34
- Assuming no conflicts, make the usual call announcing take-off (“Glider 1C take-off runway 30”)
In all cases the Line Chief should visually check for conflicting traffic, and if possible check PureTrack to look for conflicts, and make an urgent announcement if they suspect conflicts. If, after a glider has announced “take-off”, and there is no conflict the Line Chief should NOT make any radio transmission, as if it is garbled or stepped on it can only cause confusion.