Jump to content

Aspen 1000 - Intermittent Glide Slope Indication!


N205S

Recommended Posts

Good morning, all. I am working through my instrument rating in my M20J, which is equipped with an Aspen 1000 PFD, Avidyne 540, and KAP 150 Autopilot. This morning, I was hand flying a few different RNAV approaches  and during one approach the Aspen's glideslope indication was intermittently coming on and off. My Avidyne showed "LPV" and I was planning to fly the approach to LPV minimums. However, once I saw the intermittent glideslope I was prepared to fly LNAV minimums. 

The glideslope came back on and everything was fine until LPV Minimums. Still, I don't want this distraction to happen in actual IMC. Has this happened to anyone else? This was the first time it's happened to me. Any way to correct/troubleshoot this issue?

Link to comment
Share on other sites

5 hours ago, N205S said:

My Avidyne showed "LPV" and I was planning to fly the approach to LPV minimums. However, once I saw the intermittent glideslope I was prepared to fly LNAV minimums. 

A very important question to answer in order to differentially diagnose is did the Avidyne downgrade the approach? When there is loss of vertical guidance during an LPV or LNAV/VNAV the navigator should downgrade to LNAV and properly annunciate. Did this happen?

Link to comment
Share on other sites

1 hour ago, PTK said:

A very important question to answer in order to differentially diagnose is did the Avidyne downgrade the approach? When there is loss of vertical guidance during an LPV or LNAV/VNAV the navigator should downgrade to LNAV and properly annunciate. Did this happen?

The Glideslope on the Aspen only vanished for roughly +/- 1 second - and it only did it 3-4 times. When I did look over at the Avidyne Unit, it still showed LPV (but the GS indication may have been back up). It could have possibly downgraded the approach but I did not confirm since the Glide slope came back online so quickly.

I suppose my concern is more if this happened and (1) the glide slope indication didn't reappear and (2) if I were already under LNAV minimums. Hopefully this was a one time occurrence but wanted to understand/troubleshoot the problem, if this happens periodically.

Link to comment
Share on other sites

what part of the approach were you having problems? Outside the FAF or inside of it ?

LPV glideslope is a calculated value based on GPS position, there is no "real" signal to follow. It might be that the GS indicator does not display if it is outside predetermined values. 

Link to comment
Share on other sites

16 hours ago, Cruiser said:

what part of the approach were you having problems? Outside the FAF or inside of it ?

LPV glideslope is a calculated value based on GPS position, there is no "real" signal to follow. It might be that the GS indicator does not display if it is outside predetermined values. 

I had already passed the FAF and started my descent. Hopefully I can get back in the air this weekend and see if it happens again. I've got 30-40 approaches without an issue until this. I would just like to understand why this happened, troubleshoot it if possible, and have a plan incase this happens in actual IMC.

Link to comment
Share on other sites

  • 2 weeks later...
On 4/9/2020 at 7:43 AM, N205S said:

Good morning, all. I am working through my instrument rating in my M20J, which is equipped with an Aspen 1000 PFD, Avidyne 540, and KAP 150 Autopilot. This morning, I was hand flying a few different RNAV approaches  and during one approach the Aspen's glideslope indication was intermittently coming on and off. My Avidyne showed "LPV" and I was planning to fly the approach to LPV minimums. However, once I saw the intermittent glideslope I was prepared to fly LNAV minimums. 

The glideslope came back on and everything was fine until LPV Minimums. Still, I don't want this distraction to happen in actual IMC. Has this happened to anyone else? This was the first time it's happened to me. Any way to correct/troubleshoot this issue?

Ring out wiring connections for Up/Down and check the configuration on Diagnostic page for both Avidyne and Aspen.

Link to comment
Share on other sites

On 4/10/2020 at 6:52 AM, N205S said:

I had already passed the FAF and started my descent. Hopefully I can get back in the air this weekend and see if it happens again. I've got 30-40 approaches without an issue until this. I would just like to understand why this happened, troubleshoot it if possible, and have a plan incase this happens in actual IMC.

If the 440 were to downgrade after the faf due to loss of waas for example, it won’t come back to lpv during the same approach.  It shouldn’t cycle quickly between lpv/lnav at all.  Sounds like the 440 was happy with the lpv solution the whole time.  Communication or display problem?

If this happened above LNAV mins you could use those and transition to a non precision approach, or go missed.  Below LNAV mins you’d need to execute your missed approach (or land if visual with the runway).  I’d be pretty careful continuing to LNAV mins if my display was suddenly questionable after the faf and I didn’t know why.

  • Like 2
Link to comment
Share on other sites

On 4/9/2020 at 4:57 PM, N205S said:

The Glideslope on the Aspen only vanished for roughly +/- 1 second - and it only did it 3-4 times. When I did look over at the Avidyne Unit, it still showed LPV (but the GS indication may have been back up). It could have possibly downgraded the approach but I did not confirm since the Glide slope came back online so quickly.

I suppose my concern is more if this happened and (1) the glide slope indication didn't reappear and (2) if I were already under LNAV minimums. Hopefully this was a one time occurrence but wanted to understand/troubleshoot the problem, if this happens periodically.

I have been flying behind an Aspen setup for the past 8 years with a GTN navigator. Never encountered what you are seeing. If your navigator is not indicating a LOI (Loss of Integrity) status and you are seeing LPV throughout the process, it may be some anomaly with that approach itself (unlikely) or more likely a glitch either in communication between the IFD and the Aspen or possibly the current IFD data has an error. Another thing to check. A lot of people don't check the error summary for a current database download. Instead of sending out a new database download, the error summary may indicate if a particular approach has a change or other anomaly that wasn't caught when they dispatched the database download. I would check that along with the NOTAM for the airport to make sure it isn't one of these corner cases where the glide slope may be affected in some fashion.

Once I did have a legitimate LOI on an RNAV (LPV) approach after passing the FAF. I lost all GPS signal and was greeted with the LOI and a message to use another nav source. Fortunately I had the ILS running on the second HSI.

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.