Localizer Back Course Approach? |
Post Reply |
Author | ||
mfb
Senior Member Joined: 20 Dec 2014 Location: KATW Status: Offline Points: 293 |
Post Options
Thanks(0)
Posted: 11 Dec 2015 at 11:27am |
|
I have an IFD540 installed with an Aspen PFD and Century 2000 autopilot. I just did a practice localizer back course approach with this setup. I found the system behavior to be interesting. Normally, with a back course approach, you set the HSI course to the bearing of the front course. That means that the HSI course selector points backwards and, since the signal is backwards too, you don't get reverse sensing, like you would with a non-HSI nav indicator. When you are shooting front course localizer/ILS approaches with the IFD540 and the Aspen, the 540 automatically sets the bearing selector on the Aspen HSI, so you don't have to touch it. I was expecting it to do the same on the back course, and thought it would be smart enough to flip the course selector upside down. Not so. While we were being vectored for the approach, the 540 was in GPS mode and it set the course selector to the inbound course of the back course. (Not upside down.) When we got close to the final approach course it went to GPS->VLOC mode, as expected. When we intercepted the final approach, the 540 went to green VLOC mode, as it should. However, it did NOT flip the OBS upside down. So we got reverse sensing and the autopilot promptly went the wrong way and we went way off course. I was able to use the course selector knob on the Aspen to flip the OBS manually and then I selected REV mode on the autopilot. Everything was fine after that. The thing that was unexpected was the requirement to flip the course selector manually just as the 540 goes to VLOC mode. That's kind of a busy time. I don't know if that's documented anywhere. I recognize that backcourse approaches are probably being buried with the dinosaurs. The runway that I was on had a GPS approach which I would have used if I hadn't been practicing. But, as an old pilot I knew used to say when we practiced with ridiculous crosswinds, "some day you might really have to do it." Maybe this is something Avidyne should look into on the next release. What do you think the OBS should do? Stay the same or flip automatically? Mike |
||
oskrypuch
Senior Member Joined: 09 Nov 2012 Location: CYFD Status: Offline Points: 3061 |
Post Options
Thanks(0)
|
|
Now, of course you always need to check the CRS, whether it is auto-ed or not, but that is an interesting issue, it could very well create a gotcha. * Orest |
||
mfb
Senior Member Joined: 20 Dec 2014 Location: KATW Status: Offline Points: 293 |
Post Options
Thanks(0)
|
|
I was watching the OBS and I knew that the 540 had it set to the back course inbound course. I knew it hadn't flipped it. But at first I thought that the 540 was doing some sort of internal magic to reverse the signal, since it was programmed for a back course. It knew we were on a back course, so maybe it would reverse the sensing automatically. It doesn't. Mike |
||
DavidBunin
Senior Member Joined: 20 May 2015 Location: Rockwall, TX Status: Offline Points: 742 |
Post Options
Thanks(0)
|
|
When the pilot sets the OBS "down" instead of "up" on the CDI, that is the signal to the 540 that you are on a back course. So regardless of what procedure is selected in the flight plan, the 540 didn't "know" you were on a back course until you moved the OBS. That is the cue for the 540. David
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Old topic but interesting since my home field uses a back course localizer most of the time.
I’ve noticed my 540 won’t automatically go to VLOC at times. It does so when I hand fly the approach and flip the OBS to the front course on my HSI, but my Century III as luck would have it flies a beautiful back course in REV mode if I leave the OBS set to the back course. I tried it today to verify. You guys are spot on.
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Ps. Since the approach is called a back course I would’ve expected the box to know that.
|
||
rolfe_tessem
Senior Member Joined: 06 Jan 2012 Location: Massachusetts Status: Offline Points: 190 |
Post Options
Thanks(0)
|
|
I have re-read the above posts several times, and I'm still not clear.
Autopilot operation aside, do you set the HSI for the front course or the back course? My autopilot has a REV mode, so I would expect to engage that. Here in the northeast US, I don't know of an actual BC approach still in service, so the last one I did for real was several years ago in Tucson, AZ. Rolfe |
||
AZ Flyer
Senior Member Joined: 12 Feb 2018 Location: Tucson, AZ Status: Offline Points: 164 |
Post Options
Thanks(0)
|
|
I have flown the BC at Tucson for training purposes a few times, and the operation of the IFD 540, Aspen and STEC 30 is indeed interesting.
Edited by AZ Flyer - 25 Jan 2019 at 2:43pm |
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
Unlike a VOR, an ILS has only one course, the front course. That course is set by the ILS transmitter not the OBS. The setting of the OBS is independent of the ILS and has no effect on the CDI. Regardless of the OBS setting, the CDI will always show deviation in relation to the front course. Regardless of the aircraft position or heading, it will always show deviation in relation to the front course. There is no such thing as reverse sensing. The autopilot will sense the deviation in regard to the front course and correct accordingly; the setting of the OBS be damned. The statement: “…[The
540] did NOT flip the OBS upside down. So we got reverse sensing and the
autopilot promptly went the wrong way and we went way off course…” makes a
connection between the OBS and autopilot that does not exist. With the OBS pointer “flipped upside down” on
the reciprocal of the back course, the autopilot will still turn in the wrong
direction even though, to the pilot, the “picture” of the CDI looks correct.
Edited by Bob H - 25 Jan 2019 at 6:06pm |
||
Bob
|
||
rolfe_tessem
Senior Member Joined: 06 Jan 2012 Location: Massachusetts Status: Offline Points: 190 |
Post Options
Thanks(0)
|
|
Yes, I get that but is it not true that the behavior of a standard CDI and an HSI is different? I have always been taught that the HSI does not have reverse sensing -- it is always set to the front course and the needle will behave normally (as it does on the front course). This is obviously not strictly an IFD thing, but it would be good to know what the interaction between the two actually is. ("set" in this case meaning for reference and possibly for the autopilot). Rolfe |
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
|
||
Bob
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
Edited by Bob H - 26 Jan 2019 at 2:14pm |
||
Bob
|
||
AZ Flyer
Senior Member Joined: 12 Feb 2018 Location: Tucson, AZ Status: Offline Points: 164 |
Post Options
Thanks(0)
|
|
This is very helpful, thanks. It explains well why I can see the HSI moving as expected when set to the front course, but the autopilot (without REV function) doesn't turn the direction needed to stay on the localizer BC. I had already pretty much concluded that the only way I could use the autopilot for the BC is with the heading bug, and this further confirms the correctness of that conclusion.
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Hi Bob, I have tried it both ways practicing in VFR conditions. It does not work that way! Forgetting the autopilot for a moment here’s how it works at my home field KSMX Santa Maria, Ca localizer DME back course alpha approach to runway 30: 1. Select approach and activate. 2. Dial front course 120 degrees on HSI OBS 3. Reversing the OBS triggers the auto localizer (gps to loc) on the 540 4. King HSI will then work normally. If needle goes left, fly left. Right for right. 5. Hand fly the approach. The Century III will not accurately track the course in this configuration regardless of which item is selected on the coupler. If one wants to fly a coupled back course approach with the C-III and 540 it works as follows: 1. Select approach and activate. 2. Dial in back course 300 on HSI OBS. 3. When appropriate manually select VLOC on the 540. 4. Select REV on the autopilot and it will join and track the localizer back course. This is in accordance with the C-III Pilots guide.
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
#4: Are you saying that the HSI changes the way it operates when the OBS is reversed (#3)? I agree that a reversed OBS properly represents the direction to turn, but only because the pilot's view of the deviation gets reversed along with the OBS pointer. #5: Interesting. Where was your heading bug set during this? See below.
1. Course deviation is independent of OBS setting. An ILS or LOC back course can be flown with the OBS set to any magnetic bearing. 2. An HSI and standard CDI behave identically. They always show deviation in regard to the front course. 3. On a backcourse, an HSI can be set to show proper deviation direction by setting the pointer to the front course. This simply moves the CDI deviation bar from one side of the aircraft to the other. The deviation itself remains on the same side of the OBS needle. It is a visual perspective change only. I'm open to a differing opinion if someone thinks I'm mistaken. Jim, thanks for the C-III insight. |
||
Bob
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Bob,
I think we are saying the same thing with regards to the King HSI, but we’re using different terminology. I’m focused on what the pilot sees. Needle goes left, fly left to re-center the needle and be back on course. Where we disagree is with regards to the Century III. The C-III will NOT track a back course localizer in any coupler configuration (LOC NORM or LOC REV) if the OBS is set to the front course. The heading bug is not relevant. The C-III will accurately track a back course localizer IF the OBS is set to the inbound back course (300 degrees in my specific example) and the pilot MANUALLY selects VLOC (because the 540 will not auto transition unless the FRONT course is dialed in AND the pilot selects LOC REV on the Century coupler. The heading bug doesn’t matter much after intercept has been accomplished but I use it to remind myself of the appropriate inbound course. Quite frankly these back course localizer approaches could be done much more easily using the GPS. In my specific example the waypoints already exist in the FAA database! Then again I think the FAA could come up with an LPV that would replace the back course approach entirely (and it’s 3 step down fixes) that might result in lower minimums and would be easier to navigate. The biggest problem I suspect most folks have with the back course approaches is they aren’t in widespread use so folks don’t get much practice with them. I’ve owned my Bonanza for 29 years and only in the past year or so have I begun experimenting with using the autopilot for a B/C approach (in VFR conditions) trying to figure out how to make it work. Jim
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
Jim, I agree with you about the C-III. Sorry if my note wasn’t clear. I've never had to do a BC approach, but good to discuss the particulars. There's always something to learn. I mentioned that the heading bug must be set to the inbound course because the C-III manual requires it. “…DG must be set to correspond with the desired magnetic track…” “…by setting the DG Course Indicator to match the Omni Course selection, all headings are then controlled by the radio signals.” “…In principle, the radio coupler provides a heading signal which corresponds to the direction of the course to be flown. This heading signal is coupled to a radio deviation signal in such a manner that any radio deviation will cause a proportional heading deviation.” The two deviation signals work together to establish proper intercept angles and course capture without overshoot. However, when the heading is within 15 deg of course, the heading deviation signal is removed from the circuit to allow tracking the course with a crosswind. That allows the “radio deviation signal” to 100% control the heading within +/- 15 deg of the course. So, within +/- 15 deg of course, the heading bug has no affect. Outside of that 30 deg window, it certainly does. |
||
Bob
|
||
nrproces
Senior Member Joined: 19 Sep 2016 Location: Marion, MT Status: Offline Points: 142 |
Post Options
Thanks(0)
|
|
FYI Just a small reminder for those folks who have never "actually" done a BC approach. Because the localizer antenna is now on your end of the runway the actual "physical" width of the course is smaller, relative to the position that you are on final, and thereby much more sensitive to changes in heading, a normal correction is going to appear to you, the pilot, as a much more aggressive change in CDI movement. Please go out and fly some before you actually do it in the weather, so that you don't give your vestibular apparatus a serious once over near minimums. JMO (The width of the navigational ray can span from 3° to 6°, however mostly
5° are used. The output is set to secure a signal approximately 700 ft
(213, 36 m) normal approach end of the runway, on the borderline . The width of the output
magnifies, so at a distance of 10 nm (18,52 km) from the transmitter the output is about 1 nm (1,852 km) wide. So if you subtract that space from the distance on your runway [perhaps a mile or two less] you will understand why it is more sensitive when the antenna is on your end of the runway.) Edited by nrproces - 03 Feb 2019 at 7:34am |
||
Sauce
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Bob, here is a copy of the entire page of the C-III pilot’s guide regarding back course approaches. Note that the guide assumes that the aircraft begins the approach on the front course, flies past the airport, does a procedure turn, then returns on the back course.
ILS APPROACH--BACK COURSE (See Fig. 19) 1. To Intercept A. Dial ILS Back Course outbound heading on Course Selector D.G. B. When stabilized, position mode selector to LOC NORM mode. 2. After interception and when beyond fix, position mode selector to HDG and dial outbound procedure turn heading. 3. After one minute, dial inbound procedure turn heading indirection of turn. 4. When between 90° and 45° to inbound course, dial inbound course on Course Selector D.G. and position mode selector on LOC REV mode. 5. Approximately 1⁄2 mile away from runway, position mode selector to HDG mode to prevent “S” turn over ILS station near runway threshold. I can confirm that this procedure works as described in the aircraft. Jim
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
ILS APPROACH--BACK COURSE (See Fig. 19) 1. To Intercept A. Dial ILS Back
Course outbound heading on Course Selector D.G. B. When
stabilized, position mode selector to LOC NORM mode. 2. After interception and when beyond fix, position mode selector
to HDG and dial outbound procedure turn heading. 3. After one minute, dial inbound procedure turn heading
indirection of turn. 4. When between 90° and 45° to inbound course, dial inbound course
on Course Selector D.G. and position mode selector on LOC REV mode. 5. Approximately 1⁄2 mile away from runway, position mode selector
to HDG mode to prevent “S” turn over ILS station near runway threshold. I can confirm that this procedure works as described in the
aircraft. Also see “OMNI MODE” on page 16, and “LOCALIZER (Normal) MODE” and
“LOCALIZER (Reverse) MODE” on page 17.
All of these descriptions in the manual state that the “Course Selector
D.G." (heading bug) must be set to the inbound course. I suspect that most times LOC tracking isn’t
engaged until within +/- 15 deg of the inbound course (especially with GPS) so
the heading bug has already been removed from the circuit and no longer necessary for tracking the LOC. Proper tracking beyond that 30 deg window must have the heading bug set to the inbound course. |
||
Bob
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Bob,
All I can tell you is that once my C-III is locked onto course using LOC NORM I can spin the heading bug on my King HSI and it is ignored, the C-III tracks the CDI signal from the HSI. In flight once tracking a given course and approaching a fix where I turn I will spin the Heading bug to the new course as a reminder of on my next course. Reaching the fix I spin the CDI needle and the autopilot turns the aircraft. Until then, nothing happens re the Heading bug. It works differently in a non-HSI setup.
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
Hi Jim,
I'm sure you've tested this so no doubt it behaves as you describe. I'm just not sure why. I've been referencing the service manual which shows the HDG bug in the circuit. I have a C-III and have some tests in mind that I will run when I get out of maintenance. It will be awhile, but I'll keep you updated. In the meantime, here is the schematic that shows summing of the CDI and DG/HDG error signals that provides capability for intercept and tracking. |
||
Bob
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
I may have a different coupler. No DG, just an HSI.
|
||
SB Jim
Senior Member Joined: 30 Aug 2012 Status: Offline Points: 206 |
Post Options
Thanks(0)
|
|
Radio Couplers - When & WhyRadio couplers perform two functions in the autopilot system. First, they are an interface for an HSI system. Second they receive the radio information, where it is processed and mixed with the heading/course information. This composite signal is then passed to the amplifier for autopilot command. The following couplers are used with our standard DG (52D54M): the 1C388, 1C388M and 1C388P. The 1C388 is the older version coupler made before the use of HSIs in general aviation. Although this unit is compatible with newer CIIB and CIII autopilots, it is not recommended. Improvements in circuit design of the 1C388M have made the older couplers unreliable. The 1C388M and 1C388P are identical units inside and out except for the face plate. The 1C388P was made especially for Piper Aircraft for use in the Autocontrol and Altimatic autopilot series and is no longer in production. The next model of couplers are the ones used in ARINC (synchro) based systems. These models are the 1C388C, 1C388MC and the 1C388PC couplers. These couplers only accept heading signal (not course) from the HSI. As with the couplers mentioned earlier in regards to age and production status, the same applies to these models: the 1C388C and 1C388PC are no longer in production. The next model is the 1C388-2 used with our NSD series of HSIs. It will also work with certain models of HSIs manufactured by Sigma Tek. For specific models, contact the HSI manufacturer. The 1C388-2 has separate input lines for heading and course datum information. Operation of this coupler differs from the standard coupler, in that when intercepting a VOR or LORAN signal, the course needle will be set to the radial or bearing for the autopilot to properly track. In the reverse mode the 1C388-2 will automatically reverse radio and course sensing to the autopilot for proper LOC/BC function. The last coupler we offer is the 1C388-3 used with ARINC HSIs that have heading and course datum outputs. This coupler is also recommended when a King KI525A along with the KA52 adapter is used. We do not recommend the use of the 1C388M and the KA57 adapter when the KI525Ais installed. |
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
Excellent! There's the answer! Thanks Jim!
|
||
Bob
|
||
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |