Date: 202107
Local time of day: 1801-2400
Location: ZME.ARTCC, TN
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B MEM; Class E ZME
ATC / advisory: Center ZME
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness; Troubleshooting; Confusion
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Air Traffic Control; Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance
Contributing factors: Chart Or Publication; Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Chart Or Publication

Narrative: We [were] on the Vanze 2 Arrival into MEM and I was flying. After reviewing the arrival and expecting a south landing; we got a new ATIS with the airport now landing to the north. This required a change of FASOP Intersection to 10;000 and 230 knots. I put this in the FMS. I also read the North arrival on the RNAV approach to the FO. When we got to the top of descent; we had not been given a descent yet; so we requested lower. The FMS showed us high as we continued to ask for lower altitudes to make the crossing restriction. Eventually the controller gave us direct to FASOP Intersection. I told the FO we were already going there. Then the FO realized that we were not going to FASOP Intersection; but were going to FASON Intersection. We realized that I had put the crossing restriction in the FMS at FASON Intersection; and not FASOP Intersection!! This was the reason the FMS showed us high. This error was because there are two almost identically named intersections on the arrival; With the change of runway from South to North and having already verified the points; the names being so close in spelling make the error one that could easily be repeated by other crews. Once we corrected the crossing restrictions to the correct FASOP Intersection; we were very low and we slowed our rate of descent.Because we had already verified the points on the arrival; when we got the runway change; we verbally reviewed the changes and the need to insert the crossing restriction in the FASOP Intersection.  It was night and when I looked at the FMS; the first point that came up was FASON; which I mistook for FASOP.  Both the FO and I did not catch it.  We did not realize the mistake until we were given direct FASOP because we were requesting a descent because we thought we were high and were not going to make the crossing restriction.  I did mention the two intersection name similarities to the Controller; and told him it was a potential problem.  He said he agreed; but the fix was above his pay grade.The names of FASOP and FASON need to be changed; especially when there is a crossing restriction that needs to be entered in to the FMS. With both names so similar; it is easily to put the crossing restriction at the wrong point like we did. The runway change was the key here; as we were already set up to land to the South. Then the runway changed to land North; prompting the change to put the crossing restriction in the FMS.




Synopsis: Air carrier Captain reported similar sounding waypoints FASOP and FASON contributed to an altitude and heading deviation while on the VANZE TWO arrival to MEM airport.