Anyone know what "Vertical Path Full" error means?

[HighTowers 1,434]

I was flying at cruise, when VNAV disconnected and gave me "vertical path full" error.

 

Ive searched online and the manuals, and nothing comes up. If taken literally, it would mean there is too much vertical path information. Is that really possible? I doubt there would be limitations on that.

 

Anyhow I proceeded on course with lvl chg and adjusting as need be per the star.

 

Thanks

[rsvit 16]

Are you sure it was said "vertical path full"?

You can check messages on FCOM vol.2 11.61.1.

[HighTowers 1,434]

Yes very sure. It was after selecting a STAR into KIAD. Removing it didn't alleviate it and couldn't reenable VNAV.

 

Sent from my Nexus 7 using Tapatalk 2

 

 

[Tabs 2,790]

It means the vertical path solver wasn't able to compute a solution, which really shouldn't happen unless something's wrong with the navdata. (this isn't a real-life FMC message, it's a debug thing in ours specifically) Which KIAD STAR and which navdata provider+cycle is this?

[HighTowers 1,434]

Interesting. Perhaps the data is corrupt somewhere. I'll try an update.

 

It was the GIBBZ ONE star. 1209 cycle.

[iainsmith 9]

I've just had this fault on the ground before starting at EGLL (Heathrow) on a flight to EGPH (Edinburgh) departing from rwy 09R. Afraid I couldn't tell you the name of the STAR but it was using Navdata 1213.

 

Did you solve your problem Dave?

 

Iain Smith

[iainsmith 9]

Update. I d/loaded data 1213 again but that made no difference, the FMC still did not calculate any altitudes at each waypoint as it usually does. So I reverted to data 1212 and all is well again.

 

It's getting late here but tomorrow I'll contact Navdata and inform then of this. Whether I'll get my 20 credits back is another matter I suppose.

 

Iain Smith

[scandinavian13 5,192]

I think I've seen it before on the GIBBZ1 as well and just dismissed it. It flew it mostly fine, if I remember correctly. I'll fly it tomorrow and check back in.

Navigraph data (probably later cycle in Nov when I flew it last). When I fly it tomorrow, it'll be the current cycle.

[scandinavian13 5,192]

Flew it this morning. Unable to duplicate.

http://vataware.com/...cfm?id=10879719

 

AIRAC-1213 (DEC13JAN09/13)

Provider: Navigraph

 

Other than a DESC PATH UNACHIEVABLE message at one point (remedied by a little drag), all went just fine.

 

Iain:

I'd recommend re-running the installer as an admin. If that doesn't work, try downloading again. It could have gotten corrupted. Make sure you unzip the installer first, as well.

[iainsmith 9]

Iain:

I'd recommend re-running the installer as an admin. If that doesn't work, try downloading again. It could have gotten corrupted. Make sure you unzip the installer first, as well.

 

Thanks Kyle, I'll try that.

 

Iain

[JC75 22]

I've had this before also, think it was approaching vrmm, when I changed the star and approach due to wind change. Navdata would have been 1213.

[brian747 5]

Hmm, there were some EFB problems with AIRAC 1213. They were apparently cured by moving to v2 of the 1213 release.

 

http://www.aivlasoft.com/support/viewtopic.php?f=5&t=1182&sid=d08fc6465a85a2a9f09d6103c6558805

 

Could be a coincidence, of course.....

 

Cheers,

 

Brian

[FFT170 0]

Same problem onthe KIAD star GIBBZ 1 cycle 1301 tonight but also while trying to insert manual altitudes, FSX crash ....

[bobl454 0]

My friend and I both had it yesterday while flying into KDCA on the FRDMM1 arrival. I switched to the NUMMY1 and had no problem with that. The FRDMM1 has eighteen waypoints with alt. constraints where the NUMMY1 has only fourteen. Maybe it has something to do with having 15 or more constraints.We were both using the latest AIRAC from Navigraph (1301).

 

Bob Lyons

[HighTowers 1,434]

I having got the message since I posted it. Appears to have been corrupt data somewhere along the line. Not to mention navigraph has errors at times.