37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1159253 |
Time | |
Date | 201403 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZME.ARTCC |
State Reference | TN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Learjet 45 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Component | |
Aircraft Component | Altimeter |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 45 Flight Crew Total 15000 Flight Crew Type 3000 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Operating LR45 part 91 on second leg of four leg trip. Aircraft was previously operated under rvsm LOA and this was a sales demo flight; aircraft was not on rvsm LOA at time of operation. Captain filed four flight plans via online source to cover all legs that day. The equipment suffix entered by captain was 'G' non-rvsm. In the flight plan comments section the following was entered: non-rvsm request climb/descent through. Flight altitudes requested for the day where FL450 and FL430. First leg of trip was reposition with crew only; first officer (first officer) was pilot flying (PF); captain was pilot monitoring (pm). Notified ZFW sectors as we checked on that we where non-rvsm. ZFW informed us that flight plan strip had equipment listed as 'left'; rvsm approved; yet comments showed negative rvsm. We explained to them that we had filed as a 'G' but apparently online filing program sent it through as an 'left'. ZFW center said ok; understand we will show you as a 'G' and cleared us to FL450. Captain reviewed flight plan print out while enroute and aircraft had been listed as 'left'. We continued to notify each sector as we where handed off as to negative rvsm status. Upon landing captain checked website to confirm how we had been listed for equipment; it showed us as 'G'. We departed with captain as PF; first officer was pm; passengers onboard. Denver center inquired about our rvsm status as center strip listed us again as an 'left' yet negative rvsm was listed in comments section. First officer explained the rvsm status to denver center and reported to each sector - negative rvsm as we climbed to FL450. We had been in mem airspace at FL450 for awhile; approaching the rzc VOR area when mem queried us as to our rvsm status; we explained the flightplan equipment listing error again and controller said ok. A few minutes later a different controller came on and said we had not verbally reported negative rvsm to them when we checked in on frequency. First officer expressed our apologies again explained to him our status at which point we where told we had not reported negative rvsm to previous sector either. I thought we had but apparently not according to controller at this time the controller commented to the effect; we where misleading them with our non=rvsm status by having not verbally reported that to controller and having negative rvsm in comments section. Our response was -ok- what would you like us to do; we can't change it at this time;[and] offered our apologies again. Controller said he would be filing a report; again we responded - ok. The crew was aware that aircraft was not on an LOA at time of operation; it was briefed on the ground. Captain listed and filed the aircraft equipment as 'G' with flight plan filer. After first leg captain checked suffix in aircraft data file; it was listed as a 'G' yet came up as an 'left' to center. As trip captain it is my responsibility to ensure that each sector is notified to our negative rvsm status when we check on frequency. Obviously this did not occur with mem. I understand it's at center's pleasure that we are allowed through rvsm airspace; I make every attempt to get through it quickly as not to hinder other traffic or create a problem for traffic management. In this situation we had been at FL450 for roughly 90 minutes; center stated he saw we where non rvsm in the comments section of strip; we acknowledged we did not verbally advise him; so I am not really sure what his point with this was; except to waste my time filling this form out or possible cyaing himself!
Original NASA ASRS Text
Title: LR45 Captain reports a flight plan with equipment suffix G for non RVSM but the strip received by ATC at the various ATC Centers' shows suffix L for RVSM certified and a comment stating non RVSM. One ARTCC takes exception to this situation.
Narrative: Operating LR45 Part 91 on second leg of four leg trip. Aircraft was previously operated under RVSM LOA and this was a sales demo flight; aircraft was not on RVSM LOA at time of operation. Captain filed four flight plans via online source to cover all legs that day. The equipment suffix entered by Captain was 'G' Non-RVSM. In the flight plan comments section the following was entered: NON-RVSM REQUEST CLIMB/DESCENT THROUGH. Flight altitudes requested for the day where FL450 and FL430. First leg of trip was reposition with crew only; First Officer (FO) was pilot flying (PF); Captain was pilot monitoring (PM). Notified ZFW Sectors as we checked on that we where Non-RVSM. ZFW informed us that flight plan strip had equipment listed as 'L'; RVSM Approved; yet Comments showed Negative RVSM. We explained to them that we had filed as a 'G' but apparently online filing program sent it through as an 'L'. ZFW center said OK; understand we will show you as a 'G' and cleared us to FL450. Captain reviewed flight plan print out while enroute and aircraft had been listed as 'L'. We continued to notify each sector as we where handed off as to Negative RVSM status. Upon landing Captain checked website to confirm how we had been listed for equipment; it showed us as 'G'. We departed with Captain as PF; FO was PM; passengers onboard. Denver center inquired about our RVSM status as center strip listed us again as an 'L' yet Negative RVSM was listed in Comments section. FO explained the RVSM status to Denver center and reported to each sector - Negative RVSM as we climbed to FL450. We had been in MEM airspace at FL450 for awhile; approaching the RZC VOR area when MEM queried us as to our RVSM Status; we explained the flightplan equipment listing error again and Controller said OK. A few minutes later a different Controller came on and said we had not verbally reported Negative RVSM to them when we checked in on Frequency. FO expressed our apologies again explained to him our status at which point we where told we had not reported Negative RVSM to previous sector either. I thought we had but apparently not according to Controller at this time the Controller commented to the effect; we where misleading them with our NON=RVSM Status by having not verbally reported that to Controller and having NEGATIVE RVSM in Comments section. Our Response was -OK- what would you like us to do; we can't change it at this time;[and] offered our apologies again. Controller said he would be filing a report; again we responded - OK. The crew was aware that aircraft was not on an LOA at time of operation; it was briefed on the ground. Captain listed and filed the aircraft equipment as 'G' with flight plan filer. After first leg Captain checked suffix in aircraft data file; it was listed as a 'G' yet came up as an 'L' to Center. As trip Captain it is my responsibility to ensure that each sector is notified to our Negative RVSM status when we check on frequency. Obviously this did not occur with MEM. I understand it's at Center's pleasure that we are allowed through RVSM airspace; I make every attempt to get through it quickly as not to hinder other traffic or create a problem for traffic management. In this situation we had been at FL450 for roughly 90 minutes; center stated he saw we where NON RVSM in the Comments section of strip; we acknowledged we did not verbally advise him; so I am not really sure what his point with this was; except to waste my time filling this form out or possible CYAing himself!
Data retrieved from NASA's ASRS site 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.