Date: 201411
Local time of day: 1801-2400
Location: ZFW.ARTCC, TX
Flight conditions: VMC
Light: Night
Aircraft: A319
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZFW
ATC / advisory: Center ZFW
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Confusion
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: Our filed flight plan and PDC was PNUTS KLNDR1.  We were given the clearance 'descend to FL240' while in cruise at FL380.  While the NFP was talking to company the FP heard center calling us.  The FP responded to no avail.  Again center called.  The FP switched to COMM2 thinking maybe the transmission was on guard.  This wasn't the case since the NFP was communicating with OPS on COMM2.  The flying pilot then went back to COMM1 and responded again.  This time center answered very aggravated.  Center then asked if we were going to make our altitude window and that we were a few thousand feet above profile.  The FP then stated that we were given 'descend to FL240'.  Center then said; 'it doesn't matter'; what is your window.  At this point we were very confused because even if we were given descend via on the KLNDR1 we would have made our window at MUZZY (FL300-FL260) which was our next fix.  Our MCDU showed crossing MUZZY at FL267 on our current profile.  We then clarified we were assigned the KLNDR1.  Center told us we need to read our flight plan correctly and that we were assigned the WHINY1. We again double checked our PDC and flight plan to confirm we were correct.   He then gave us a frequency change and told us 'make the window'.  The flying pilot then asked; 'what window are we supposed to make?'  Not having time to open up the chart and reprogram the MCDU knowing that we were approaching a window rapidly based on centers urgency.  Center then gave us a lower altitude to descend to without specifying a crossing restriction.  We then switched to the next controller.  At this point the NFP took the radios and we checked in with the new center controller.  They assigned us a vector and told us to go direct to another fix when able to meet a constraint they gave us.  We proceeded direct to the fix and complied with the constraints on the WHINY1 without incident.   The original controller we were speaking to was very unprofessional; demeaning and requesting things that were not regulatory.  We were given a descend to FL240; which supersedes a descend via.  There is no reason when given a descend to FL240 the controller should have used language; 'it doesn't matter; what's your window'.  Also during our postflight review of the arrivals we saw how there could be some confusion with these two STAR's based on their names.   We were assigned the KLNDR1.  Center thought we were on the KLNDR.WHINY1.  Both arrivals have KLNDR in the name.




Synopsis: A319 First Officer describes a confusing exchange with a ZFW Controller concerning a descent clearance for an RNAV arrival. ZFW thought the flight was on the WHINY1 (KLNDR.WHINY1) and the crew thought they were on the KLNDR1 (KLNDR.KLNDER1). The confusion level was increased by a descend to FL240 clearance from ATC and not a descend via. ZFW did not mention or the crew did not detect the actual name of the RNAV arrival in use.