37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1509505 |
Time | |
Date | 201801 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Embraer Legacy 450/500 |
Operating Under FAR Part | Part 91 |
Flight Phase | Parked |
Component | |
Aircraft Component | Electronic Flt Bag (EFB) |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural MEL Deviation - Procedural Published Material / Policy |
Narrative:
Plane had an MEL that required that the engine anti-ice to be on for takeoff. I ran the numbers in my i-preflight and I thought that I had selected the 'engine 1/2 anti ice on' option for the ipreflight. When the numbers came back I thought I had valid numbers for take off. It appears that I inadvertently must have deselected the 'eng 1/2 anti ice on' option on the i-preflight screen while running the numbers for the flight. This caused me to take off with inaccurate performance information. Since I manually enter v-speeds from info on i-preflight I missed an opportunity that may have caught the error. The following morning; I was doing ipreflight planning for a series of flights to be conducted and couldn't get the numbers to work out of warmer airports due to the 'eng 1/2 anti-ice on' option on ipreflight. It is at this point I realized that I must have made an error the day before inputting my ipreflight data. First and foremost I take full responsibility; I inadvertently made an error entering data onto i-preflight. I made the input error and didn't catch it. Thinking that my 'numbers were good' I elected to fly the trip as I thought all was okay. I am a new captain and even newer to this aircraft (maybe 30-40 hours total in aircraft since I got typed in plane). This was also the first time I had flown [for some time] due to a vacation and sickness. This was the first time I had flown as a captain on an international trip and although it is not an excuse I found myself overly concerned about making sure all the customs paperwork etc. Was in order since it was my first time dealing with international flight as a captain. Additionally trying to get services at ZZZZ was very slow with passengers due to arrive (customs and catering). I found myself concerned with those issues vs sitting back for 10 minutes and reviewing my planning where I may have caught my error. [The event] has caused me to quadruple check all my numbers and variables on my ipreflight - I have never made an error of this type before and I will be sure to quadruple check my work now because of this event. Even today I have quadruple checked all of my flight plans and settings on ipreflight to make sure I won't make the same error again.1 - I may be in the minority in this department but I think a little more time in ground school for new captains going over paperwork dealing with customs/international would be a good thing - it is the one area personally that as a new captain that I wish we had a little more time going over. Most of our older captains have been in their positions for many years and customs paperwork is not a big deal but as first officer's are rarely if ever exposed to it so it adds a level to their preflight activities. Now as the first officer's are upgrading I think even a 20 -30 minute refresher course would be beneficial and make them more comfortable with it.2 - I am not sure if the flight planning department has access to/considers mels on aircraft when they do the planning for trips. If not I think that they should - as flight crews we have a lot going on before a flight with catering fueling etc. And maybe if the planning department had access to and applied any MEL considerations then it would be another level to prevent/catch operator (pilot) errors such as mine. To this extent; even after I had informed the company that we would not be able to depart out of warm area airports the company still tried to a dd a trip on the aircraft which we were not able to do out of the area due to the MEL. If planning had and applied the mels it would catch errors such as mine the previous day and would add another safety buffer to flight operations.3 - maybe an option on i-preflight stating 'all mels considered reviewed and conformed with' might be a helpful reminder to catch this error in future or even an option to select the conditions another separate time on another screen during the planning process just to catch input errors like this.4 - I personally will quadruple check my information and flight planning from here on out making sure what I think I put in is actually what has been inputted.
Original NASA ASRS Text
Title: Embraer Legacy 450 Captain reported that he inadvertently made an error entering data onto i-preflight screen which caused him to takeoff with with inaccurate performance information.
Narrative: Plane had an MEL that required that the Engine anti-ice to be on for takeoff. I ran the numbers in my i-preflight and I thought that I had selected the 'ENG 1/2 anti ice on' option for the ipreflight. When the numbers came back I thought I had valid numbers for take off. It appears that I inadvertently must have deselected the 'Eng 1/2 anti ice on' option on the i-preflight screen while running the numbers for the flight. This caused me to take off with inaccurate performance information. Since I manually enter v-speeds from info on i-preflight I missed an opportunity that may have caught the error. The following morning; I was doing ipreflight planning for a series of flights to be conducted and couldn't get the numbers to work out of warmer airports due to the 'Eng 1/2 anti-ice on' option on ipreflight. It is at this point I realized that I must have made an error the day before inputting my ipreflight data. First and foremost I take full responsibility; I inadvertently made an error entering data onto i-preflight. I made the input error and didn't catch it. Thinking that my 'numbers were good' I elected to fly the trip as I thought all was okay. I am a new captain and even newer to this aircraft (maybe 30-40 hours total in aircraft since I got typed in plane). This was also the first time I had flown [for some time] due to a vacation and sickness. This was the first time I had flown as a Captain on an international trip and although it is not an excuse I found myself overly concerned about making sure all the customs paperwork etc. was in order since it was my first time dealing with international flight as a captain. Additionally trying to get services at ZZZZ was very slow with passengers due to arrive (customs and catering). I found myself concerned with those issues vs sitting back for 10 minutes and reviewing my planning where I may have caught my error. [The event] has caused me to quadruple check all my numbers and variables on my ipreflight - I have never made an error of this type before and I will be sure to quadruple check my work now because of this event. Even today I have quadruple checked all of my flight plans and settings on ipreflight to make sure I won't make the same error again.1 - I may be in the minority in this department but I think a little more time in ground school for new captains going over paperwork dealing with customs/international would be a good thing - it is the one area personally that as a new Captain that I wish we had a little more time going over. Most of our older Captains have been in their positions for many years and customs paperwork is not a big deal but as FO's are rarely if ever exposed to it so it adds a level to their preflight activities. Now as the FO's are upgrading I think even a 20 -30 minute refresher course would be beneficial and make them more comfortable with it.2 - I am not sure if the flight planning department has access to/considers MELs on aircraft when they do the planning for trips. If not I think that they should - as flight crews we have a lot going on before a flight with catering fueling etc. and maybe if the planning department had access to and applied any MEL considerations then it would be another level to prevent/catch operator (pilot) errors such as mine. To this extent; even after I had informed the company that we would not be able to depart out of warm area airports the company still tried to a dd a trip on the aircraft which we were not able to do out of the area due to the MEL. If planning had and applied the MELs it would catch errors such as mine the previous day and would add another safety buffer to flight operations.3 - Maybe an option on i-preflight stating 'all MELs considered reviewed and conformed with' might be a helpful reminder to catch this error in future or even an option to select the conditions another separate time on another screen during the planning process just to catch input errors like this.4 - I personally will quadruple check my information and flight planning from here on out making sure what I think I put in is actually what has been inputted.
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.