The idea is to keep the landing area clear for safety when a helicopter is taking off. Before a departing helicopter lifts off, the arriving helicopter should move away from the landing area so the takeoff path isn’t in the rotor wash or flight path of the other helicopter. Waiting until the arrival has taxied off the landing area ensures the ground space is truly clear and reduces the risk of interference or collision during liftoff. If the arrival has merely landed, it might still be occupying or partially blocking the landing area, and rotor wash or tail-rotor clearance could affect the departing helicopter. Clearing the area by taxiing off is a clearer, safer condition than just “landed.” The other options don’t fit typical helicopter ground-separation practices: “cleared the runway” uses a term more associated with fixed-wing operations and isn’t the right context here, and “departed” would mean the departure has already occurred, which defeats the separation goal.

Identifying the correct option hinges on matching the required dimension to the taxiway description. The task asks for a width of 200 feet, so the statement that specifies a taxiway being 200 feet wide is the right one. Taxiway width is set to provide safe clearance for aircraft taxiing, including enough room for wings and for clearance from edges and markings. The other options describe widths of 250, 150, and 300 feet, which do not meet the 200-foot requirement.

When joining a SID with a specific transition, you state the SID name first and then the transition name after a comma. This order clearly ties the transition to that particular SID, making it unambiguous for the pilot and ATC. The example STROUDSBURG ONE DEPARTURE, SPARTA TRANSITION follows this standard format exactly. It presents the SID name, then the transition name, separated by a comma, so everyone knows which departure and which transition to fly. Other phrasings don’t fit the standard: placing the transition before the SID reverses the expected order and can create confusion about which SID is being used; using phrases like "transition via" isn’t the conventional way to specify a SID transition; and swapping the order or wording mixes up the association between the SID and its transition.

Basic radar separation is the minimum horizontal distance required between two aircraft being observed on radar. For successive IFR departures, the standard spacing is three nautical miles. This separation gives enough room to account for typical differences in climb rates, speeds, and potential track adjustments, while still allowing the radar controller to monitor both aircraft reliably and avoid conflicts as the first aircraft climbs away and the second follows. In practice, controllers ensure at least this distance before allowing the second aircraft to proceed on a similar path, sometimes adjusting speed or delaying departures to maintain the spacing. The other options don’t reflect the common standard for this situation: five miles is a broader en route separation, while two or four miles would not meet the established basic separation for successive departures.