Date: 201905
Local time of day: 1801-2400
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Dusk
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Contributing factors: Chart Or Publication; Airspace Structure; Aircraft; Company Policy; Procedure
Primary problem: Ambiguous

Narrative: While embarking on the CHSLY4 Arrival into CLT we experienced an altitude deviation. After arriving from another flight; I was informed by crew track that I was to conduct a flight from ZZZ to CLT. By the time I arrived; the flight was already boarded and ready to be pushed back. I reviewed the release; flight plan and conducted all preflight checks. The FMS route had already been populated and ATC flight clearances copied by the First Officer. We pushed back and after a short ground delay we departed ZZZ on our filed route to CLT. While on the flight our climb to our 'Final' filed cruising altitude was delayed and route modified with constant heading changes; level-offs and speed limits changes. When we finally reached our final cruising altitude of 26;000 feet we were then instructed to descend via the CHSLY4 arrival into CLT. We looked down at the FMS and started a decent to 13;000 feet (minimum crossing altitude over BOOTS); this was our next displayed fix in our FMS at that time. As we started to get the ATIS and conduct our pre-landing briefs we inadvertently descended below the crossing altitude for SKLES of 280 knots at or above FL220. We were then informed by ATC about our altitude deviation. They then instructed us to maintain flight level FL180; and then proceeded to continue our Decent via the CHSLY4 Arrival. We then reentered the arrival into FMS to discover that SKLES was not displayed in the FMS; even though other arrival fixes were displayed. We informed ATC of the issue and continued on the arrival without further issues. We were given a number to call upon landing by ATC. After calling Center we informed them about our discovery in the FMS. The Supervisor at the time informed me that this was not the first time they had seen this deviation around this area. Supervisor was not sure if it was a technical issue. He also implored me to include his comments in my report. I thanked him; took his information down and informed him of my agreement to fill out a report. The next flight back continued later without further issues or complications. To prevent this from occurring again as a crew we should brief the SIDS and STARS and their restrictions; and anticipated landing runways before departing the original airport. The arrival and correct runway should be later briefed again on the 'In Range' portion in the check list to ensure all altitude and speed windows are properly displayed in the FMS.




Synopsis: Air carrier Captain reported experiencing an altitude deviation while on the CHSLY4 RNAV STAR due to SKLES fix dropping out of their FMS.  Reportedly; this is a common occurrence.