37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 474264 |
Time | |
Date | 200005 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : zme.artcc |
State Reference | TN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zme.artcc |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude climbout : vacating altitude cruise : level |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : multi engine pilot : cfi |
Experience | flight time last 90 days : 200 flight time total : 2500 flight time type : 250 |
ASRS Report | 474264 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 232 flight time total : 7592 flight time type : 315 |
ASRS Report | 474250 |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued alert other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This was the last day of 4 straight days of flying. The previous day we flew over 7 1/2 hours involving ground delays, in-flight deviations and holding due to thunderstorms. Today we were scheduled for almost 6 hours of flying. This was the second flight of the day from bna to iad. This flight was filed with the following route: bna...hvq...JASEN2.iad. When clearance delivery issued our clearance it was: 'cleared the nashville 8 departure, as filed, maintain 5000 ft, departure frequency is 118.4, squawk XXXX.' this is what we inputted into the FMS computer and flew. There is a second route that we often fly, it is: bna...swapp.J42.bkw.JASEN2.iad. Once we were airborne, departure issued several vector headings. The final one was to 'maintain...to join...' because of fatigue, I cannot recall if he said '...to join the jet route' or '...to join your route.' I answered back verbatim what he stated, and set the heading into the FMS computer. The issued heading was a 30 degree intercept to our filed routing and looked like a good intercept heading. The FMS does not distinguish between direct routing or jet routes. We were then handed off to center control. Center acknowledged our initial call and said nothing of our position or heading. Approximately 20 mins later center inquired if we were on the jet route. I was confused by his question, but replied that we filed via direct routing and clearance delivery had stated 'cleared as filed.' center then stated that we should have been on the jet routing, he gave us vectors so we did not conflict with other traffic, and stated he would have to look into this. At no time were there any conflicts or other dangers to aircraft. We continued with our direct routing with no other problems.
Original NASA ASRS Text
Title: FLC OF A CANADAIR, CL65 CRJ, FOLLOWED THEIR FILED FLT PLAN RATHER THAN THE FLT PLAN CLRNC GIVEN PRIOR TO DEP RESULTING IN ATC VECTORS TO AVOID OTHER TFC.
Narrative: THIS WAS THE LAST DAY OF 4 STRAIGHT DAYS OF FLYING. THE PREVIOUS DAY WE FLEW OVER 7 1/2 HRS INVOLVING GND DELAYS, INFLT DEVS AND HOLDING DUE TO TSTMS. TODAY WE WERE SCHEDULED FOR ALMOST 6 HRS OF FLYING. THIS WAS THE SECOND FLT OF THE DAY FROM BNA TO IAD. THIS FLT WAS FILED WITH THE FOLLOWING RTE: BNA...HVQ...JASEN2.IAD. WHEN CLRNC DELIVERY ISSUED OUR CLRNC IT WAS: 'CLRED THE NASHVILLE 8 DEP, AS FILED, MAINTAIN 5000 FT, DEP FREQ IS 118.4, SQUAWK XXXX.' THIS IS WHAT WE INPUTTED INTO THE FMS COMPUTER AND FLEW. THERE IS A SECOND RTE THAT WE OFTEN FLY, IT IS: BNA...SWAPP.J42.BKW.JASEN2.IAD. ONCE WE WERE AIRBORNE, DEP ISSUED SEVERAL VECTOR HEADINGS. THE FINAL ONE WAS TO 'MAINTAIN...TO JOIN...' BECAUSE OF FATIGUE, I CANNOT RECALL IF HE SAID '...TO JOIN THE JET RTE' OR '...TO JOIN YOUR RTE.' I ANSWERED BACK VERBATIM WHAT HE STATED, AND SET THE HEADING INTO THE FMS COMPUTER. THE ISSUED HEADING WAS A 30 DEG INTERCEPT TO OUR FILED ROUTING AND LOOKED LIKE A GOOD INTERCEPT HEADING. THE FMS DOES NOT DISTINGUISH BTWN DIRECT ROUTING OR JET ROUTES. WE WERE THEN HANDED OFF TO CTR CTL. CTR ACKNOWLEDGED OUR INITIAL CALL AND SAID NOTHING OF OUR POS OR HEADING. APPROX 20 MINS LATER CTR INQUIRED IF WE WERE ON THE JET RTE. I WAS CONFUSED BY HIS QUESTION, BUT REPLIED THAT WE FILED VIA DIRECT ROUTING AND CLRNC DELIVERY HAD STATED 'CLRED AS FILED.' CTR THEN STATED THAT WE SHOULD HAVE BEEN ON THE JET ROUTING, HE GAVE US VECTORS SO WE DID NOT CONFLICT WITH OTHER TFC, AND STATED HE WOULD HAVE TO LOOK INTO THIS. AT NO TIME WERE THERE ANY CONFLICTS OR OTHER DANGERS TO ACFT. WE CONTINUED WITH OUR DIRECT ROUTING WITH NO OTHER PROBS.
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.