What prevents the use of a multi-segment ILS for non-straight approaches?
$begingroup$
An ILS, consisting of a localiser beam to provide lateral guidance (which can also be used on its own for a non-precision approach) and a glideslope beam to provide vertical guidance, is (currently) indispensable for precision approaches in IMC, but comes with a few disadvantages.
Chief among those is the fact that an ILS only supports approaches that are ramrod-straight all the way in from the outer marker, when such an approach path is often impossible or undesirable...
- ...sometimes because something too solid to fly through is in the way (for instance, the infamous approach to runway 13 at Kai Tak, which, due to an inconveniently-placed mountain, necessitated coming in at a large angle to the runway and then making a sharp right turn at very low altitude at almost literally the last moment; an instrument guidance system - basically an ILS without the “landing” part - was added in the 1970s to provide precision guidance for the part of the approach before the turn, but the turn itself and the final approach segment still had to be hand-flown visually, an exceptionally difficult task even in good weather)...
- ...and sometimes because someone else is using part of the airspace in question (for instance, the four major airports in the New York area [JFK, la Guardia, Newark, and Teterboro] have numerous intersecting approach paths, which, as the approaches can’t be bent or segmented to keep out of each others’ way, frequently forces la Guardia and Teterboro to land aircraft on runways with strong crosswinds [because the ILS approach paths for their more optimal runways would risk causing MACs with aircraft on ILS approaches into JFK and/or Newark]; on the other side of the continent, the approach paths coming into LAX from the east pass near or over Ontario, which has caused quite a number of near misses in the vicinity of the latter airport).
It doesn’t seem, conceptually, like it should be too hard to break up an ILS approach into two or more segments, each with its own localiser and glideslope, and with the beams from the pre- and post-bend segments intersecting at the bend in the approach path. As most aircraft are unable to turn on a dime, they would need to start turning a bit before the bend in the approach, but this could be easily handled by having another instrumental aid (for instance, a third localiser) indicate when to start turning; if the bend in the approach were sharp enough for the aircraft to have trouble locking onto the post-bend beams, another localiser and glideslope, with their beams tangent to the midpoint of the turn, could be used to assist the aircraft round the bend.
All of this would also work for segmented localiser approaches, with the added advantage of being easier to implement (no need for the multiple glideslope antennae, just the localiser ones).
Here be an illustration of what I’ve got in mind:
Why aren’t segmented ILS and localiser approaches used in practice?
approach ils localizer
$endgroup$
add a comment |
$begingroup$
An ILS, consisting of a localiser beam to provide lateral guidance (which can also be used on its own for a non-precision approach) and a glideslope beam to provide vertical guidance, is (currently) indispensable for precision approaches in IMC, but comes with a few disadvantages.
Chief among those is the fact that an ILS only supports approaches that are ramrod-straight all the way in from the outer marker, when such an approach path is often impossible or undesirable...
- ...sometimes because something too solid to fly through is in the way (for instance, the infamous approach to runway 13 at Kai Tak, which, due to an inconveniently-placed mountain, necessitated coming in at a large angle to the runway and then making a sharp right turn at very low altitude at almost literally the last moment; an instrument guidance system - basically an ILS without the “landing” part - was added in the 1970s to provide precision guidance for the part of the approach before the turn, but the turn itself and the final approach segment still had to be hand-flown visually, an exceptionally difficult task even in good weather)...
- ...and sometimes because someone else is using part of the airspace in question (for instance, the four major airports in the New York area [JFK, la Guardia, Newark, and Teterboro] have numerous intersecting approach paths, which, as the approaches can’t be bent or segmented to keep out of each others’ way, frequently forces la Guardia and Teterboro to land aircraft on runways with strong crosswinds [because the ILS approach paths for their more optimal runways would risk causing MACs with aircraft on ILS approaches into JFK and/or Newark]; on the other side of the continent, the approach paths coming into LAX from the east pass near or over Ontario, which has caused quite a number of near misses in the vicinity of the latter airport).
It doesn’t seem, conceptually, like it should be too hard to break up an ILS approach into two or more segments, each with its own localiser and glideslope, and with the beams from the pre- and post-bend segments intersecting at the bend in the approach path. As most aircraft are unable to turn on a dime, they would need to start turning a bit before the bend in the approach, but this could be easily handled by having another instrumental aid (for instance, a third localiser) indicate when to start turning; if the bend in the approach were sharp enough for the aircraft to have trouble locking onto the post-bend beams, another localiser and glideslope, with their beams tangent to the midpoint of the turn, could be used to assist the aircraft round the bend.
All of this would also work for segmented localiser approaches, with the added advantage of being easier to implement (no need for the multiple glideslope antennae, just the localiser ones).
Here be an illustration of what I’ve got in mind:
Why aren’t segmented ILS and localiser approaches used in practice?
approach ils localizer
$endgroup$
add a comment |
$begingroup$
An ILS, consisting of a localiser beam to provide lateral guidance (which can also be used on its own for a non-precision approach) and a glideslope beam to provide vertical guidance, is (currently) indispensable for precision approaches in IMC, but comes with a few disadvantages.
Chief among those is the fact that an ILS only supports approaches that are ramrod-straight all the way in from the outer marker, when such an approach path is often impossible or undesirable...
- ...sometimes because something too solid to fly through is in the way (for instance, the infamous approach to runway 13 at Kai Tak, which, due to an inconveniently-placed mountain, necessitated coming in at a large angle to the runway and then making a sharp right turn at very low altitude at almost literally the last moment; an instrument guidance system - basically an ILS without the “landing” part - was added in the 1970s to provide precision guidance for the part of the approach before the turn, but the turn itself and the final approach segment still had to be hand-flown visually, an exceptionally difficult task even in good weather)...
- ...and sometimes because someone else is using part of the airspace in question (for instance, the four major airports in the New York area [JFK, la Guardia, Newark, and Teterboro] have numerous intersecting approach paths, which, as the approaches can’t be bent or segmented to keep out of each others’ way, frequently forces la Guardia and Teterboro to land aircraft on runways with strong crosswinds [because the ILS approach paths for their more optimal runways would risk causing MACs with aircraft on ILS approaches into JFK and/or Newark]; on the other side of the continent, the approach paths coming into LAX from the east pass near or over Ontario, which has caused quite a number of near misses in the vicinity of the latter airport).
It doesn’t seem, conceptually, like it should be too hard to break up an ILS approach into two or more segments, each with its own localiser and glideslope, and with the beams from the pre- and post-bend segments intersecting at the bend in the approach path. As most aircraft are unable to turn on a dime, they would need to start turning a bit before the bend in the approach, but this could be easily handled by having another instrumental aid (for instance, a third localiser) indicate when to start turning; if the bend in the approach were sharp enough for the aircraft to have trouble locking onto the post-bend beams, another localiser and glideslope, with their beams tangent to the midpoint of the turn, could be used to assist the aircraft round the bend.
All of this would also work for segmented localiser approaches, with the added advantage of being easier to implement (no need for the multiple glideslope antennae, just the localiser ones).
Here be an illustration of what I’ve got in mind:
Why aren’t segmented ILS and localiser approaches used in practice?
approach ils localizer
$endgroup$
An ILS, consisting of a localiser beam to provide lateral guidance (which can also be used on its own for a non-precision approach) and a glideslope beam to provide vertical guidance, is (currently) indispensable for precision approaches in IMC, but comes with a few disadvantages.
Chief among those is the fact that an ILS only supports approaches that are ramrod-straight all the way in from the outer marker, when such an approach path is often impossible or undesirable...
- ...sometimes because something too solid to fly through is in the way (for instance, the infamous approach to runway 13 at Kai Tak, which, due to an inconveniently-placed mountain, necessitated coming in at a large angle to the runway and then making a sharp right turn at very low altitude at almost literally the last moment; an instrument guidance system - basically an ILS without the “landing” part - was added in the 1970s to provide precision guidance for the part of the approach before the turn, but the turn itself and the final approach segment still had to be hand-flown visually, an exceptionally difficult task even in good weather)...
- ...and sometimes because someone else is using part of the airspace in question (for instance, the four major airports in the New York area [JFK, la Guardia, Newark, and Teterboro] have numerous intersecting approach paths, which, as the approaches can’t be bent or segmented to keep out of each others’ way, frequently forces la Guardia and Teterboro to land aircraft on runways with strong crosswinds [because the ILS approach paths for their more optimal runways would risk causing MACs with aircraft on ILS approaches into JFK and/or Newark]; on the other side of the continent, the approach paths coming into LAX from the east pass near or over Ontario, which has caused quite a number of near misses in the vicinity of the latter airport).
It doesn’t seem, conceptually, like it should be too hard to break up an ILS approach into two or more segments, each with its own localiser and glideslope, and with the beams from the pre- and post-bend segments intersecting at the bend in the approach path. As most aircraft are unable to turn on a dime, they would need to start turning a bit before the bend in the approach, but this could be easily handled by having another instrumental aid (for instance, a third localiser) indicate when to start turning; if the bend in the approach were sharp enough for the aircraft to have trouble locking onto the post-bend beams, another localiser and glideslope, with their beams tangent to the midpoint of the turn, could be used to assist the aircraft round the bend.
All of this would also work for segmented localiser approaches, with the added advantage of being easier to implement (no need for the multiple glideslope antennae, just the localiser ones).
Here be an illustration of what I’ve got in mind:
Why aren’t segmented ILS and localiser approaches used in practice?
approach ils localizer
approach ils localizer
asked 4 hours ago
SeanSean
5,33932667
5,33932667
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
$begingroup$
See here, pages 5-23, 5-24. Things have advanced well beyond ILS for that kind of approach.
https://whispertrack.com/pdf/faa_handbook.pdf
REQUIRED NAVIGATION PERFORMANCE
The operational advantages of RNP include accuracy
and integrity monitoring, which provide more precision and lower minimums than conventional RNAV.
RNP DAs can be as low as 250 feet with visibilities as
low as 3/4 SM. Besides lower minimums, the benefits
of RNP include improved obstacle clearance limits, as
well as reduced pilot workload. When RNP-capable
aircraft fly an accurate, repeatable path, ATC can be
confident that these aircraft will be at a specific position, thus maximizing safety and increasing capacity
To attain the benefits of RNP approach procedures, a
key component is curved flight tracks. Constant radius
turns around a fix are called “radius-to-fix legs,” or RF
legs. These turns, which are encoded into the navigation database, allow the aircraft to avoid critical areas
of terrain or conflicting airspace while preserving positional accuracy by maintaining precise, positive course
guidance along the curved track. The introduction of
RF legs into the design of terminal RNAV procedures
results in improved use of airspace and allows procedures to be developed to and from runways that are otherwise limited to traditional linear flight paths or, in
some cases, not served by an IFR procedure at all.
Navigation systems with RF capability are a prerequisite to flying a procedure that includes an RF leg. Refer
to the notes box of the pilot briefing portion of the
approach chart in figure 5-17.
The Approach in Fig 5-17 has 5 turns left & right!
$endgroup$
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "528"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faviation.stackexchange.com%2fquestions%2f61538%2fwhat-prevents-the-use-of-a-multi-segment-ils-for-non-straight-approaches%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
See here, pages 5-23, 5-24. Things have advanced well beyond ILS for that kind of approach.
https://whispertrack.com/pdf/faa_handbook.pdf
REQUIRED NAVIGATION PERFORMANCE
The operational advantages of RNP include accuracy
and integrity monitoring, which provide more precision and lower minimums than conventional RNAV.
RNP DAs can be as low as 250 feet with visibilities as
low as 3/4 SM. Besides lower minimums, the benefits
of RNP include improved obstacle clearance limits, as
well as reduced pilot workload. When RNP-capable
aircraft fly an accurate, repeatable path, ATC can be
confident that these aircraft will be at a specific position, thus maximizing safety and increasing capacity
To attain the benefits of RNP approach procedures, a
key component is curved flight tracks. Constant radius
turns around a fix are called “radius-to-fix legs,” or RF
legs. These turns, which are encoded into the navigation database, allow the aircraft to avoid critical areas
of terrain or conflicting airspace while preserving positional accuracy by maintaining precise, positive course
guidance along the curved track. The introduction of
RF legs into the design of terminal RNAV procedures
results in improved use of airspace and allows procedures to be developed to and from runways that are otherwise limited to traditional linear flight paths or, in
some cases, not served by an IFR procedure at all.
Navigation systems with RF capability are a prerequisite to flying a procedure that includes an RF leg. Refer
to the notes box of the pilot briefing portion of the
approach chart in figure 5-17.
The Approach in Fig 5-17 has 5 turns left & right!
$endgroup$
add a comment |
$begingroup$
See here, pages 5-23, 5-24. Things have advanced well beyond ILS for that kind of approach.
https://whispertrack.com/pdf/faa_handbook.pdf
REQUIRED NAVIGATION PERFORMANCE
The operational advantages of RNP include accuracy
and integrity monitoring, which provide more precision and lower minimums than conventional RNAV.
RNP DAs can be as low as 250 feet with visibilities as
low as 3/4 SM. Besides lower minimums, the benefits
of RNP include improved obstacle clearance limits, as
well as reduced pilot workload. When RNP-capable
aircraft fly an accurate, repeatable path, ATC can be
confident that these aircraft will be at a specific position, thus maximizing safety and increasing capacity
To attain the benefits of RNP approach procedures, a
key component is curved flight tracks. Constant radius
turns around a fix are called “radius-to-fix legs,” or RF
legs. These turns, which are encoded into the navigation database, allow the aircraft to avoid critical areas
of terrain or conflicting airspace while preserving positional accuracy by maintaining precise, positive course
guidance along the curved track. The introduction of
RF legs into the design of terminal RNAV procedures
results in improved use of airspace and allows procedures to be developed to and from runways that are otherwise limited to traditional linear flight paths or, in
some cases, not served by an IFR procedure at all.
Navigation systems with RF capability are a prerequisite to flying a procedure that includes an RF leg. Refer
to the notes box of the pilot briefing portion of the
approach chart in figure 5-17.
The Approach in Fig 5-17 has 5 turns left & right!
$endgroup$
add a comment |
$begingroup$
See here, pages 5-23, 5-24. Things have advanced well beyond ILS for that kind of approach.
https://whispertrack.com/pdf/faa_handbook.pdf
REQUIRED NAVIGATION PERFORMANCE
The operational advantages of RNP include accuracy
and integrity monitoring, which provide more precision and lower minimums than conventional RNAV.
RNP DAs can be as low as 250 feet with visibilities as
low as 3/4 SM. Besides lower minimums, the benefits
of RNP include improved obstacle clearance limits, as
well as reduced pilot workload. When RNP-capable
aircraft fly an accurate, repeatable path, ATC can be
confident that these aircraft will be at a specific position, thus maximizing safety and increasing capacity
To attain the benefits of RNP approach procedures, a
key component is curved flight tracks. Constant radius
turns around a fix are called “radius-to-fix legs,” or RF
legs. These turns, which are encoded into the navigation database, allow the aircraft to avoid critical areas
of terrain or conflicting airspace while preserving positional accuracy by maintaining precise, positive course
guidance along the curved track. The introduction of
RF legs into the design of terminal RNAV procedures
results in improved use of airspace and allows procedures to be developed to and from runways that are otherwise limited to traditional linear flight paths or, in
some cases, not served by an IFR procedure at all.
Navigation systems with RF capability are a prerequisite to flying a procedure that includes an RF leg. Refer
to the notes box of the pilot briefing portion of the
approach chart in figure 5-17.
The Approach in Fig 5-17 has 5 turns left & right!
$endgroup$
See here, pages 5-23, 5-24. Things have advanced well beyond ILS for that kind of approach.
https://whispertrack.com/pdf/faa_handbook.pdf
REQUIRED NAVIGATION PERFORMANCE
The operational advantages of RNP include accuracy
and integrity monitoring, which provide more precision and lower minimums than conventional RNAV.
RNP DAs can be as low as 250 feet with visibilities as
low as 3/4 SM. Besides lower minimums, the benefits
of RNP include improved obstacle clearance limits, as
well as reduced pilot workload. When RNP-capable
aircraft fly an accurate, repeatable path, ATC can be
confident that these aircraft will be at a specific position, thus maximizing safety and increasing capacity
To attain the benefits of RNP approach procedures, a
key component is curved flight tracks. Constant radius
turns around a fix are called “radius-to-fix legs,” or RF
legs. These turns, which are encoded into the navigation database, allow the aircraft to avoid critical areas
of terrain or conflicting airspace while preserving positional accuracy by maintaining precise, positive course
guidance along the curved track. The introduction of
RF legs into the design of terminal RNAV procedures
results in improved use of airspace and allows procedures to be developed to and from runways that are otherwise limited to traditional linear flight paths or, in
some cases, not served by an IFR procedure at all.
Navigation systems with RF capability are a prerequisite to flying a procedure that includes an RF leg. Refer
to the notes box of the pilot briefing portion of the
approach chart in figure 5-17.
The Approach in Fig 5-17 has 5 turns left & right!
answered 2 hours ago
CrossRoadsCrossRoads
4,9101819
4,9101819
add a comment |
add a comment |
Thanks for contributing an answer to Aviation Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faviation.stackexchange.com%2fquestions%2f61538%2fwhat-prevents-the-use-of-a-multi-segment-ils-for-non-straight-approaches%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown