 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767 captain reported having flown to destination that is not authorized in the company ops specs.
| Attributes | |
| ACN | 1605114 |
| Time | |
| Date | 201812 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Dawn |
| Aircraft 1 | |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Operated aircraft X inbound and outbound in violation of [company] ops spec and 14CFR 121.55. Ops spec allows only for the B757 to be used as an [X] airport. At the time the 767 was listed in said ops specs as an [Y] airport; for the B767 ZZZ authorization was for use as an alternate only. While it is my responsibility to be familiar with all aspects of the fom and ops specs it is difficult to be cognizant of every airfield in [them]. The B757 is used frequently to service ZZZ. It would not have and did not raise a flag that the B767 was not authorized. Especially considering the company published the [dispatch packet] with this trip built prior to my operating. In [many] years with the company; I have never come across this situation. It was common practice to double check alternates for authorization. It did not occur to me that an operational flight plan would be filed and subsequently accepted to an airfield not authorized for the B767. Especially a flight pairing published in a [dispatch packet] (built by the company) and an operational flight plan filed and subsequently accepted to an airfield not authorized for the B767. Due to this wrong assumption; I operated the flight inbound and outbound in violation. In the future; if I have not operated a flight previously into a gateway I will reference ops specs.
Original NASA ASRS Text
Title: B767 Captain reported having flown to destination that is not authorized in the company Ops Specs.
Narrative: Operated Aircraft X inbound and outbound in violation of [Company] Ops Spec and 14CFR 121.55. Ops Spec allows only for the B757 to be used as an [X] airport. At the time the 767 was listed in said Ops Specs as an [Y] airport; for the B767 ZZZ authorization was for use as an Alternate only. While it is my responsibility to be familiar with all aspects of the FOM and Ops Specs it is difficult to be cognizant of every airfield in [them]. The B757 is used frequently to service ZZZ. It would not have and did not raise a flag that the B767 was not authorized. Especially considering the company published the [dispatch packet] with this trip built prior to my operating. In [many] years with the company; I have never come across this situation. It was common practice to double check Alternates for authorization. It did not occur to me that an operational flight plan would be filed and subsequently accepted to an airfield not authorized for the B767. Especially a flight pairing published in a [dispatch packet] (built by the company) and an operational flight plan filed and subsequently accepted to an airfield not authorized for the B767. Due to this wrong assumption; I operated the flight inbound and outbound in violation. In the future; if I have not operated a flight previously into a gateway I will reference Ops Specs.
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.