Hello all, as the topic suggests, I had an issue with RNP I think. I have only had the airplane a few hours and since I'm leaving on a real airplane in 4 hours, haven't had much time to read up on the manual. Because RNP is something completely new to FS, this was the first time I had ever tried a full RNP approach. So here's how I tested it:First, ran the RNP rwy 19 into KDCA. Everything was going well until I passed over JTSON waypoint. Once I passed JTSON, the aircraft did a complet right 360 to get back to SETOC waypoint instead of going direct. I had the APP mode armed and GP was in green on the FMA. FAC was still white and LNAV was in use....I'm assuming FAC means Final Approach Course and because it wasn't yet a straight in, it couldn't engage. Once I hit WIRSO, FAC turned green and the airplane started turning rapidly. Ok, so that one didn't go so well, I tried something simpler.Then tried the RNP to rwy 1 into KDCA, everything went perfect until about 100 ft when the plane again started to make turns and disengaged the AP. I had both CMD A and B engaged and CMD was green on the FMA.Am I just not doing something right or is there a possible issue with RNP. I was under the assumption that RNP could be used as another form of autoland.

I had the same thing happen with the RNP 19 KDCA. In fact it seemed i still had a screen showing the very thing: Uploaded with ImageShack.us

RNAV approaches are not able to use auto land, they have minimums. Auto land must be preformed using radio signals (and carefully aligned ones at that, CATIII aproaches). Even being 0.3 off (in the case of KDCA RNAV RWY1) in nav performance would be a bad thing for allowing the aircraft to fly itself to the ground.

To the last part of OP's post: The chart says minimums of 386 feet for RNP 1 KDCA. If I'm correct that means you have to hand fly it from there to the RWY. Which is also depicted by the solid line from MRION via OXONN ending at minimums and transitioning to Missed Approach. i.e. the automated part stops there