Citation V/Ultra/Encore (C560)
Human-Machine Interface; Distraction; Confusion; Communication Breakdown; Situational Awareness; Training / Qualification
ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Provided Assistance
Chart Or Publication; Human Factors; Staffing; Procedure
The Citation was on the SWFFT arrival at BNA and we were landing south [Runways 2L; C; R.] The pilot seemed confused by the RNAV procedures and when I questioned why he wasn't descending when he declared he was stopping at 6;000 FT as a hard altitude instead of 5;000 FT as published he said he was waiting until CORRA.After he got midfield downwind instead of heading 020 as published he turned due east on his own and the final [Controller] had to bring him back out of my airspace.This kind of stuff happens all the time on the RNAV. I know I write a lot about it but I'm getting fatigued using up my break time to document it. You have to extrapolate this to the other 40 controllers here who don't bother to file safety reports about it.Our management is actively hiding the problem because they want to look good in the eyes of the new 'Magnolia' hub. I'm about done filing about it; myself. From now on I'll be ignoring the problems and working around them just like I was told to by my Supervisor--unless there is an actual loss of separation and I need the protections [afforded by the safety reporting system].Sorry to have wasted your time.
An Approach Controller described what he professes to be one of numerous instances of flight crew inability and/or failure to comply with the OPD RNAV STAR procedures at BNA. He further vented his frustration to his Superiors' lack of responsiveness to this and previous reports he has submitted; citing what he feels to be a preference for political canoodling over problem solving.