A commuter flight crew read back wrong airway and proceeded to intercept the wrong airway, after dep...

Attributes
ACN	321490
Time
Date	199511
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : djb airport : cle
State Reference	OH
Altitude	msl bound lower : 6000 msl bound upper : 6000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cle tower : iad
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : initial
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : cfi pilot : commercial
Experience	flight time last 90 days : 250 flight time total : 1650 flight time type : 200
ASRS Report	321490
Person 2
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 : 5000 flight time type : 800
ASRS Report	321671
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : returned to intended course or assigned course other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Initial clearance was as filed, and filed route was radar vectors fails, V443 doggs, direct to yxu V98 ywt, V216. After takeoff, we were cleared right turn 330 degrees, intercept V443, climb to 11000 ft. We read back 'intercept V435.' no correction was given. We then misinterpreted the chart and flew a heading to intercept the 074 degree radial off of djb. After intercept, approach asked 'where are you going?' he issued an immediate turn clearance to 030 degrees, and a new altitude of 6000 ft. At this time we complied and he then reclred us to 18000 ft. We flew the 030 degree heading to intercept V443. Shortly before intercepting V443, the controller again asked us what our heading was. We replied '030 degrees' and that we were turning onto V443. At hand-off, we apologized for the mistake but got no answer from approach and assume a violation has been filed. Additional contributing factors include our preset expectation of radar vectors to fails before joining the airway, and the fact that our readback was for V435, which doesn't exist northeast of djb, was not corrected (caused a scramble for a radial of which 074 degree was mistakenly chosen as V435 due to its proximity opposite to djb VOR). Human performance was possibly affected by the fact that the captain had flown the late shift the day before and was on reduced rest for this morning shift block of flts. The schedule was different from routine and I the first officer was behind the power curve mentally from wake up and was just catching up at the time of the incident. Supplemental information from acn 321671: when the first officer accepted clearance on the ground as 'as filed' I assumed the routing was a continuation to yyz (our destination) from ind (the same) and did not check out the proper filed flight plan out of cle. Also assumed the first officer knew the filed flight plan since he had gotten the clearance, an assumption on my part I should have not assumed.

Original NASA ASRS Text

Title: A COMMUTER FLC READ BACK WRONG AIRWAY AND PROCEEDED TO INTERCEPT THE WRONG AIRWAY, AFTER DEP. DEP CTLR INTERVENED. TRACK DEV. DEV FROM CLRNC RTE.

Narrative: INITIAL CLRNC WAS AS FILED, AND FILED RTE WAS RADAR VECTORS FAILS, V443 DOGGS, DIRECT TO YXU V98 YWT, V216. AFTER TKOF, WE WERE CLRED R TURN 330 DEGS, INTERCEPT V443, CLB TO 11000 FT. WE READ BACK 'INTERCEPT V435.' NO CORRECTION WAS GIVEN. WE THEN MISINTERPRETED THE CHART AND FLEW A HDG TO INTERCEPT THE 074 DEG RADIAL OFF OF DJB. AFTER INTERCEPT, APCH ASKED 'WHERE ARE YOU GOING?' HE ISSUED AN IMMEDIATE TURN CLRNC TO 030 DEGS, AND A NEW ALT OF 6000 FT. AT THIS TIME WE COMPLIED AND HE THEN RECLRED US TO 18000 FT. WE FLEW THE 030 DEG HDG TO INTERCEPT V443. SHORTLY BEFORE INTERCEPTING V443, THE CTLR AGAIN ASKED US WHAT OUR HDG WAS. WE REPLIED '030 DEGS' AND THAT WE WERE TURNING ONTO V443. AT HAND-OFF, WE APOLOGIZED FOR THE MISTAKE BUT GOT NO ANSWER FROM APCH AND ASSUME A VIOLATION HAS BEEN FILED. ADDITIONAL CONTRIBUTING FACTORS INCLUDE OUR PRESET EXPECTATION OF RADAR VECTORS TO FAILS BEFORE JOINING THE AIRWAY, AND THE FACT THAT OUR READBACK WAS FOR V435, WHICH DOESN'T EXIST NE OF DJB, WAS NOT CORRECTED (CAUSED A SCRAMBLE FOR A RADIAL OF WHICH 074 DEG WAS MISTAKENLY CHOSEN AS V435 DUE TO ITS PROXIMITY OPPOSITE TO DJB VOR). HUMAN PERFORMANCE WAS POSSIBLY AFFECTED BY THE FACT THAT THE CAPT HAD FLOWN THE LATE SHIFT THE DAY BEFORE AND WAS ON REDUCED REST FOR THIS MORNING SHIFT BLOCK OF FLTS. THE SCHEDULE WAS DIFFERENT FROM ROUTINE AND I THE FO WAS BEHIND THE PWR CURVE MENTALLY FROM WAKE UP AND WAS JUST CATCHING UP AT THE TIME OF THE INCIDENT. SUPPLEMENTAL INFO FROM ACN 321671: WHEN THE FO ACCEPTED CLRNC ON THE GND AS 'AS FILED' I ASSUMED THE ROUTING WAS A CONTINUATION TO YYZ (OUR DEST) FROM IND (THE SAME) AND DID NOT CHK OUT THE PROPER FILED FLT PLAN OUT OF CLE. ALSO ASSUMED THE FO KNEW THE FILED FLT PLAN SINCE HE HAD GOTTEN THE CLRNC, AN ASSUMPTION ON MY PART I SHOULD HAVE NOT ASSUMED.

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.

A commuter flight crew read back wrong airway and proceeded to intercept the wrong airway, after departure. Departure controller intervened. Track deviation. Deviation from clearance route.