 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
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.
| Attributes | |
| ACN | 1065714 |
| Time | |
| Date | 201302 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | BNA.Airport |
| State Reference | TN |
| Aircraft 1 | |
| Make Model Name | Citation V/Ultra/Encore (C560) |
| Flight Phase | Descent Final Approach |
| Route In Use | STAR SWFFT1 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
The citation was on the swfft arrival at bna and we were landing south [runways 2L; C; right.] 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.
Original NASA ASRS Text
Title: 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.
Narrative: 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.
Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.