Narrative:

Pilot deviation due to inputting incorrect flight plan into FMS.aircraft X; routine flight from ZZZ to ZZZ2. Typically; crew meets in ZZZ an hour and a half before departure; conducts preflight; including flight planning together; then we taxi from one side of the airport to the terminal side to await passengers. Once there; we brief and review all our instruments are ready for departure before; during; and after passengers are boarding. Once we decide we are ready; we close the door and depart. All duties are usually distributed between the captain and first officer (first officer).this morning; instead of our typical meet up in ZZZ; we began a half hour earlier in ZZZ1 (a nearby airport). We had to reposition to ZZZ to pick up the passengers. We sometimes have issues with gate availability so we have to time our departure properly in order to ensure our designated gate is available to use and that our team will be able to meet us upon arrival.upon arrival to the ZZZ1 airport; both the captain and the flight attendant had already arrived and begun the preflight duties. I greet the captain and ask if he needs help with the flight planning; he said he had completed it already and was about to print. I went to a different computer and printed something I needed. As soon as I finished; the captain asked me to go begin the preflight. I gathered my things and got started. Once our general preflight checks were done (the walk-around and interior checks such as our stall protection system; fire tests; etc.); I began to set up the flights deck for our specific flight in terms of our performance; FMS; etc. As I am putting in the flight plan; the captain places about 6 papers (all our flight plans for the day) in the center console and says we're going direct to ZZZ. I say great and I plug it into the computer without needing to check the physical paper since I was familiar with the route. I prepared everything ahead of time for our short flight; including our landing performance and approach information for ZZZ before even starting our engines in ZZZ1. Before beginning our checklists; we organize all paperwork into either the flight can; or the captain puts it in his folder to prevent things from getting lost (including the flight plans). We departed right on time and the flight was short and sweet. However; during our final approach into ZZZ; we got an inbd brk inoperative message. Without enough time to conduct a checklist; we decided that we had enough runway to stop with only thrust reversers if necessary and chose to continue the approach. We landed with no problem and the captain reported that the brakes operated normally. However; since we had an indication in the cockpit; we would not be able to depart without it being cleared. We physically checked the brakes upon arrival to our gate and before passengers boarded and everything looked normal. I told the captain and he replied that we needed to do a hard reset; like turning a computer off and back on again. Once everything came back on; the message extinguished and we were able to continue the flight. However; doing a hard reset means that the preflight checks have to be conducted again. The captain asked me to get the clearance and set up the flight deck for departure while he dealt with paperwork and the weight and balance. We were cleared to ZZZ2 with radar vectors for the X departure; then as filed. Considering our company does this flight every [week; and used to be even more frequent]; I had no reason to think that this flight would be any different. This is the only flight route that is stored/saved in our FMS. So I immediately put in the stored route; checked it with the canned route that I have written down and continued our checks/setup. Once everything was done and passengers were boarded; we conducted the checklists; which ask about FMS setup more than once; I said it's set. Basically; the captain has no reason to not believe me considering he thought he had shown me the flight plan earlier that morning (when I actually did not even look at it because I didn't think I needed to. I knew the route; I knew the airports; operationally everything was going the same). Also; the captain has been doing the same route for past two months almost every week while this is the first time I had flown this route in over a month. Apparently somewhere along the line; the route that center would clear us through to go to ZZZ2 changed and while the captain had been using the new routes for the past couple of weeks; it wasn't new to him anymore; and I didn't know anything had changed. It was complete miscommunication and poor CRM. I should have definitely checked the flight plan and the captain should have checked my work. Ultimately you can imagine both of our surprise when center calls us about a quarter into the flight and asks us where we're going and I just plainly say 'zzzzz' and the captain looks over to me with wide eyes and just says 'what?! You've got to be kidding me' (or something along those lines). We eventually put two and two together; and came to the conclusion that I had no idea I had done anything wrong until after the fact and neither did the captain. Considering we used our previous routing so often; it also didn't 'click' that something was off when we passed a fix and headed toward the incorrect fix. We immediately asked for a vector in the right direction and got the correct route put in within a couple seconds. This was only the second leg of the day and we had 4 more to go. After everything settled and we had a little time; I went into the FMS and immediately deleted the stored flight plan route (to hopefully prevent something like that from happening to another crew) and discussed with the captain at how we could prevent it. I apologized and decided that something like this would never happen again by improving our briefings; double-checking; and creating better habits when conducting routine flights like always using the flight plan route to crosscheck not just a list of the companies canned routes.all in all; after correcting the route; center called us again to write down a number for a possible pilot deviation. Ultimately these are some of the major factors that contributed to this mistake:- short preflight briefing; not thorough enough- complacency due to routine flight- captain not double checking work of first officer- not using correct paperwork to input informationalso; it's important to note that the rest of the flights were completed safely; professionally; and with absolutely no issues despite our frustration and confusion during the beginning of our day.

Related reports:

Google
 

Original NASA ASRS Text

Title: E-145 First Officer reported a track deviation occurred when the FMS route was improperly loaded.

Narrative: Pilot deviation due to inputting incorrect flight plan into FMS.Aircraft X; routine flight from ZZZ to ZZZ2. Typically; crew meets in ZZZ an hour and a half before departure; conducts preflight; including flight planning together; then we taxi from one side of the airport to the terminal side to await passengers. Once there; we brief and review all our instruments are ready for departure before; during; and after passengers are boarding. Once we decide we are ready; we close the door and depart. All duties are usually distributed between the Captain and FO (First Officer).This morning; instead of our typical meet up in ZZZ; we began a half hour earlier in ZZZ1 (a nearby airport). We had to reposition to ZZZ to pick up the passengers. We sometimes have issues with gate availability so we have to time our departure properly in order to ensure our designated gate is available to use and that our team will be able to meet us upon arrival.Upon arrival to the ZZZ1 airport; both the Captain and the flight attendant had already arrived and begun the preflight duties. I greet the Captain and ask if he needs help with the flight planning; he said he had completed it already and was about to print. I went to a different computer and printed something I needed. As soon as I finished; the Captain asked me to go begin the preflight. I gathered my things and got started. Once our general preflight checks were done (the walk-around and interior checks such as our stall protection system; fire tests; etc.); I began to set up the flights deck for our specific flight in terms of our performance; FMS; etc. As I am putting in the flight plan; the Captain places about 6 papers (all our flight plans for the day) in the center console and says we're going direct to ZZZ. I say great and I plug it into the computer without needing to check the physical paper since I was familiar with the route. I prepared everything ahead of time for our short flight; including our landing performance and approach information for ZZZ before even starting our engines in ZZZ1. Before beginning our checklists; we organize all paperwork into either the flight can; or the Captain puts it in his folder to prevent things from getting lost (including the flight plans). We departed right on time and the flight was short and sweet. However; during our final approach into ZZZ; we got an INBD BRK INOP message. Without enough time to conduct a checklist; we decided that we had enough runway to stop with only thrust reversers if necessary and chose to continue the approach. We landed with no problem and the Captain reported that the brakes operated normally. However; since we had an indication in the cockpit; we would not be able to depart without it being cleared. We physically checked the brakes upon arrival to our gate and before passengers boarded and everything looked normal. I told the Captain and he replied that we needed to do a hard reset; like turning a computer off and back on again. Once everything came back on; the message extinguished and we were able to continue the flight. However; doing a hard reset means that the preflight checks have to be conducted again. The Captain asked me to get the clearance and set up the flight deck for departure while he dealt with paperwork and the weight and balance. We were cleared to ZZZ2 with radar vectors for the X Departure; then as filed. Considering our company does this flight every [week; and used to be even more frequent]; I had no reason to think that this flight would be any different. This is the only flight route that is stored/saved in our FMS. So I immediately put in the stored route; checked it with the canned route that I have written down and continued our checks/setup. Once everything was done and passengers were boarded; we conducted the checklists; which ask about FMS setup more than once; I said it's set. Basically; the Captain has no reason to not believe me considering he thought he had shown me the flight plan earlier that morning (when I actually did not even look at it because I didn't think I needed to. I knew the route; I knew the airports; operationally everything was going the same). Also; the Captain has been doing the same route for past two months almost every week while this is the first time I had flown this route in over a month. Apparently somewhere along the line; the route that Center would clear us through to go to ZZZ2 changed and while the Captain had been using the new routes for the past couple of weeks; it wasn't new to him anymore; and I didn't know anything had changed. It was complete miscommunication and poor CRM. I should have definitely checked the flight plan and the Captain should have checked my work. Ultimately you can imagine both of our surprise when Center calls us about a quarter into the flight and asks us where we're going and I just plainly say 'ZZZZZ' and the captain looks over to me with wide eyes and just says 'what?! You've got to be kidding me' (or something along those lines). We eventually put two and two together; and came to the conclusion that I had no idea I had done anything wrong until after the fact and neither did the Captain. Considering we used our previous routing so often; it also didn't 'click' that something was off when we passed a fix and headed toward the incorrect fix. We immediately asked for a vector in the right direction and got the correct route put in within a couple seconds. This was only the second leg of the day and we had 4 more to go. After everything settled and we had a little time; I went into the FMS and immediately deleted the stored flight plan route (to hopefully prevent something like that from happening to another crew) and discussed with the Captain at how we could prevent it. I apologized and decided that something like this would never happen again by improving our briefings; double-checking; and creating better habits when conducting routine flights like always using the flight plan route to crosscheck not just a list of the companies canned routes.All in all; after correcting the route; Center called us again to write down a number for a possible pilot deviation. Ultimately these are some of the major factors that contributed to this mistake:- Short preflight briefing; not thorough enough- Complacency due to routine flight- Captain not double checking work of FO- Not using correct paperwork to input informationAlso; it's important to note that the rest of the flights were completed safely; professionally; and with absolutely no issues despite our frustration and confusion during the beginning of our day.

Data retrieved from NASA's ASRS site 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.