37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 204951 |
Time | |
Date | 199203 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : ord |
State Reference | IL |
Altitude | msl bound lower : 5000 msl bound upper : 8000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : ord tower : sea |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
Experience | controller radar : 10 |
ASRS Report | 204951 |
Person 2 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
Events | |
Anomaly | aircraft equipment problem : less severe altitude deviation : overshoot conflict : airborne less severe non adherence : published procedure non adherence : far non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance flight crew : overcame equipment problem |
Consequence | faa : investigated faa : assigned or threatened penalties |
Miss Distance | horizontal : 18000 vertical : 0 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Air carrier X departed O'hare on a 140 degree assigned heading. Air carrier X did not check in on departure control. I attempted, several times, to turn air carrier X around an airspace boundary but got no response. I checked with the tower controller. The center sector and another departure controller to see if they were talking to air carrier X. No one had the aircraft however west departure had been getting a carrier with no modulation several times and so he transmitted in the blind for air carrier X to contact departure on the appropriate frequency (which is published on the only SID O'hare has). I, then, received a carrier with no modulation and assumed it was air carrier X so I transmitted to air carrier X to turn immediately to 220 degree because the aircraft was going head-on to another aircraft which was being turned out of the way. I then said 'if that's air carrier X trying to call, try another radio because the one you're on is not working.' I then got the first understandable call from air carrier X and immediately asked him his altitude. Pilot replies 7500 ft. I then asked what he was climbing to and he replied 10000. When I asked where he got 10000 from he said he got it from the tower. After reviewing the tapes, air carrier X did not ever contact clearance delivery as required. Air carrier X was told by ground control and local control that he had radio problems and to try another radio. Air carrier X did not use his call sign when accepting his takeoff clearance and then went to the wrong published frequency for departure. The ord 9 departure assigns 5000 ft to all departures and air carrier X climbed to 10000 ft without checking in with departure control. The approach controller took evasive action to avoid a conflict with air carrier X so separation was not lost. The crew of air carrier X displayed a very unprofessional and unsafe attitude not to mention violating several far's. A pilot deviation report was filed.
Original NASA ASRS Text
Title: MLG FLC DEP ORD IGNORES RADIO PROBLEMS ON THE GND, DEPARTS WITHOUT RTE CLRNC, LOSES XMIT CAPABILITY WHEN AIRBORNE, AND FAILS TO SWITCH TO DEP CTL FREQ AFTER TKOF. POTENTIAL CONFLICT WITH OTHER ACR WHEN RPTR CTLR IS TRYING TO ESTABLISH CONTACT WITH MLG.
Narrative: ACR X DEPARTED O'HARE ON A 140 DEG ASSIGNED HDG. ACR X DID NOT CHK IN ON DEP CTL. I ATTEMPTED, SEVERAL TIMES, TO TURN ACR X AROUND AN AIRSPACE BOUNDARY BUT GOT NO RESPONSE. I CHKED WITH THE TWR CTLR. THE CTR SECTOR AND ANOTHER DEP CTLR TO SEE IF THEY WERE TALKING TO ACR X. NO ONE HAD THE ACFT HOWEVER W DEP HAD BEEN GETTING A CARRIER WITH NO MODULATION SEVERAL TIMES AND SO HE XMITTED IN THE BLIND FOR ACR X TO CONTACT DEP ON THE APPROPRIATE FREQ (WHICH IS PUBLISHED ON THE ONLY SID O'HARE HAS). I, THEN, RECEIVED A CARRIER WITH NO MODULATION AND ASSUMED IT WAS ACR X SO I XMITTED TO ACR X TO TURN IMMEDIATELY TO 220 DEG BECAUSE THE ACFT WAS GOING HEAD-ON TO ANOTHER ACFT WHICH WAS BEING TURNED OUT OF THE WAY. I THEN SAID 'IF THAT'S ACR X TRYING TO CALL, TRY ANOTHER RADIO BECAUSE THE ONE YOU'RE ON IS NOT WORKING.' I THEN GOT THE FIRST UNDERSTANDABLE CALL FROM ACR X AND IMMEDIATELY ASKED HIM HIS ALT. PLT REPLIES 7500 FT. I THEN ASKED WHAT HE WAS CLBING TO AND HE REPLIED 10000. WHEN I ASKED WHERE HE GOT 10000 FROM HE SAID HE GOT IT FROM THE TWR. AFTER REVIEWING THE TAPES, ACR X DID NOT EVER CONTACT CLRNC DELIVERY AS REQUIRED. ACR X WAS TOLD BY GND CTL AND LCL CTL THAT HE HAD RADIO PROBLEMS AND TO TRY ANOTHER RADIO. ACR X DID NOT USE HIS CALL SIGN WHEN ACCEPTING HIS TKOF CLRNC AND THEN WENT TO THE WRONG PUBLISHED FREQ FOR DEP. THE ORD 9 DEP ASSIGNS 5000 FT TO ALL DEPS AND ACR X CLBED TO 10000 FT WITHOUT CHKING IN WITH DEP CTL. THE APCH CTLR TOOK EVASIVE ACTION TO AVOID A CONFLICT WITH ACR X SO SEPARATION WAS NOT LOST. THE CREW OF ACR X DISPLAYED A VERY UNPROFESSIONAL AND UNSAFE ATTITUDE NOT TO MENTION VIOLATING SEVERAL FAR'S. A PLTDEV RPT WAS FILED.
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.