Narrative:

Our flight to kbwi was filed as: bkw RAVNN5 kbwi. Shortly after departure we were cleared direct to bkw. Once on with potomac approach we were cleared to yaegr intersection and cleared to descend via the RAVNN5 arrival. Near caash intersection the approach controller asked 'if we were authorized the arrival;' we replied 'yes.' the approach controlled asked 'under what far are you operating under?' we replied 'far part 135.' the approach controller then told us the RAVNN5 arrival was not authorized for far part 91; 101; 103; 105; 125; 133; 135; and 137. We were given a left turn to 360 and a descent to FL190. We were then cleared direct bubbi and then via the ANTHM1 arrival. The controller asked if our approach plates showed the restriction; and because of our work level sequencing ourselves unto a new arrival at an intermediate fix we stated 'no.' we told potomac approach that we would take a closer look at the RAVNN5 arrival on the ground and communicate with our company that we are not authorized to file or fly the arrival. We continued with the ANTHM1 arrival and landed at kbwi without further queries.upon a closer look at the RAVNN5 arrival into kbwi we did in fact find small print regarding the far part 91; 101; 103; 105; 125; 133; 135; and 137 restriction. We assume that the ravnn 5 is not authorized due to presidential security. Although we were not in close proximity to restricted area 6611A.going forward [flight planning] should be notified that we are unable to fly the RAVNN5 arrival into bwi. I will also take it upon myself to be more diligent when reviewing all approach plates for restrictions.

Google
 

Original NASA ASRS Text

Title: CE-750 pilot reported planning to fly the RAVNN5 arrival to BWI until ATC advised him it was not authorized for his flight that was operating under FAR Part 135.

Narrative: Our flight to KBWI was filed as: BKW RAVNN5 KBWI. Shortly after departure we were cleared direct to BKW. Once on with Potomac Approach we were cleared to YAEGR intersection and cleared to descend via the RAVNN5 arrival. Near CAASH intersection the Approach Controller asked 'if we were authorized the arrival;' we replied 'yes.' The Approach Controlled asked 'under what FAR are you operating under?' We replied 'FAR Part 135.' The Approach Controller then told us the RAVNN5 arrival was not authorized for FAR Part 91; 101; 103; 105; 125; 133; 135; and 137. We were given a left turn to 360 and a descent to FL190. We were then cleared direct BUBBI and then via the ANTHM1 arrival. The controller asked if our approach plates showed the restriction; and because of our work level sequencing ourselves unto a new arrival at an intermediate fix we stated 'No.' We told Potomac Approach that we would take a closer look at the RAVNN5 arrival on the ground and communicate with our company that we are not authorized to file or fly the arrival. We continued with the ANTHM1 arrival and landed at KBWI without further queries.Upon a closer look at the RAVNN5 arrival into KBWI we did in fact find small print regarding the FAR Part 91; 101; 103; 105; 125; 133; 135; and 137 restriction. We assume that the RAVNN 5 is not authorized due to presidential security. Although we were not in close proximity to Restricted Area 6611A.Going forward [flight planning] should be notified that we are unable to fly the RAVNN5 arrival into BWI. I will also take it upon myself to be more diligent when reviewing all approach plates for restrictions.

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.