 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of medium large transport question if they received clearance via ACARS or were flying without a clearance.
| Attributes | |
| ACN | 194743 |
| Time | |
| Date | 199111 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phl |
| State Reference | PA |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : ord |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | climbout : takeoff cruise other ground : preflight |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : commercial pilot : instrument |
| Experience | flight time last 90 days : 180 flight time total : 15000 flight time type : 1300 |
| ASRS Report | 194743 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 180 flight time total : 7000 flight time type : 300 |
| ASRS Report | 194730 |
| Events | |
| Anomaly | non adherence : clearance non adherence : far non adherence : published procedure |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
| Situations | |
| ATC Facility | procedure or policy : unspecified |
Narrative:
Possible departure from phl airport without en route clearance having been received from clearance delivery. Clearance was not written down nor was it on the ACARS message screen and flight crew did not recall receiving it once they were airborne. Wrong transponder code was on transponder and when they looked to get departure control frequency they could not find clearance. Tower cleared aircraft for takeoff and shifted to departure control who took handoff normally. ATC facilities did not mention possible lack of en route clearance to crew and no problems were encountered, however, crew felt they had overlooked obtaining the necessary en route clearance and felt uncomfortable about the possibility of this occurring. Could this be a problem when getting pre-departure clearance using ACARS and how does ground control, tower, etc, know we have actually received the clearance after they have put it into pacer?
Original NASA ASRS Text
Title: FLC OF MLG QUESTION IF THEY RECEIVED CLRNC VIA ACARS OR WERE FLYING WITHOUT A CLRNC.
Narrative: POSSIBLE DEP FROM PHL ARPT WITHOUT ENRTE CLRNC HAVING BEEN RECEIVED FROM CLRNC DELIVERY. CLRNC WAS NOT WRITTEN DOWN NOR WAS IT ON THE ACARS MESSAGE SCREEN AND FLC DID NOT RECALL RECEIVING IT ONCE THEY WERE AIRBORNE. WRONG TRANSPONDER CODE WAS ON TRANSPONDER AND WHEN THEY LOOKED TO GET DEP CTL FREQ THEY COULD NOT FIND CLRNC. TWR CLRED ACFT FOR TKOF AND SHIFTED TO DEP CTL WHO TOOK HDOF NORMALLY. ATC FACILITIES DID NOT MENTION POSSIBLE LACK OF ENRTE CLRNC TO CREW AND NO PROBLEMS WERE ENCOUNTERED, HOWEVER, CREW FELT THEY HAD OVERLOOKED OBTAINING THE NECESSARY ENRTE CLRNC AND FELT UNCOMFORTABLE ABOUT THE POSSIBILITY OF THIS OCCURRING. COULD THIS BE A PROBLEM WHEN GETTING PRE-DEP CLRNC USING ACARS AND HOW DOES GND CTL, TWR, ETC, KNOW WE HAVE ACTUALLY RECEIVED THE CLRNC AFTER THEY HAVE PUT IT INTO PACER?
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.