37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 331715 |
Time | |
Date | 199603 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : enev |
State Reference | FO |
Altitude | msl bound lower : 85 msl bound upper : 2460 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : enev |
Operator | common carrier : air carrier |
Make Model Name | DC-10 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | descent : approach |
Route In Use | approach : visual arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 350 flight time total : 12000 flight time type : 2000 |
ASRS Report | 331715 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 350 flight time total : 12000 flight time type : 2000 |
ASRS Report | 332009 |
Events | |
Anomaly | non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
We the flight crew were never trained on the terrain or the special 3.8 degree GS. To me this was very much a special airport, however there never was any data indicating such from company or elsewhere. This airport also did not have a SID or a published IFR departure in my communication manual. The only reference we had was in our load manual that really dealt more with climb out with an engine failure than normal IFR departure. Obviously to us this airport needs a published IFR departure. On further inspection, we found several airports in the area with no published IFR departure. The dangerous thing here is, we were cleared on course, which was right into a mountain, when the only obvious course out of there was out the fjord. Luckily for us it was day VFR. Also after the fact we were dispatched on a trip that took us within 100 NM of magnetic unreliability. Our operations specifications refers to operations in mnps airspace excluding airspace of magnetic unreliability as listed in canadian aip. Our operations didn't have a copy. Therefore it was just luck we didn't enter this prohibitive airspace.
Original NASA ASRS Text
Title: CAPT OF A WDB COMPLAINS OF NOT HAVING COMPANY TRAINING ON RTES AND ARPTS OVER, AND INTO, FOREIGN RTE AND ARPT.
Narrative: WE THE FLC WERE NEVER TRAINED ON THE TERRAIN OR THE SPECIAL 3.8 DEG GS. TO ME THIS WAS VERY MUCH A SPECIAL ARPT, HOWEVER THERE NEVER WAS ANY DATA INDICATING SUCH FROM COMPANY OR ELSEWHERE. THIS ARPT ALSO DID NOT HAVE A SID OR A PUBLISHED IFR DEP IN MY COM MANUAL. THE ONLY REF WE HAD WAS IN OUR LOAD MANUAL THAT REALLY DEALT MORE WITH CLBOUT WITH AN ENG FAILURE THAN NORMAL IFR DEP. OBVIOUSLY TO US THIS ARPT NEEDS A PUBLISHED IFR DEP. ON FURTHER INSPECTION, WE FOUND SEVERAL ARPTS IN THE AREA WITH NO PUBLISHED IFR DEP. THE DANGEROUS THING HERE IS, WE WERE CLRED ON COURSE, WHICH WAS RIGHT INTO A MOUNTAIN, WHEN THE ONLY OBVIOUS COURSE OUT OF THERE WAS OUT THE FJORD. LUCKILY FOR US IT WAS DAY VFR. ALSO AFTER THE FACT WE WERE DISPATCHED ON A TRIP THAT TOOK US WITHIN 100 NM OF MAGNETIC UNRELIABILITY. OUR OPS SPECS REFERS TO OPS IN MNPS AIRSPACE EXCLUDING AIRSPACE OF MAGNETIC UNRELIABILITY AS LISTED IN CANADIAN AIP. OUR OPS DIDN'T HAVE A COPY. THEREFORE IT WAS JUST LUCK WE DIDN'T ENTER THIS PROHIBITIVE AIRSPACE.
Data retrieved from NASA's ASRS site as of July 2007 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.