Narrative:

During takeoff and after V1 we noticed a failure of the copilot's airspeed. This was apparent due to IAS comparison monitor on both mfd's and the copilot's airspeed being completely off from what the left side and standby readouts read. We continued the climb ran the checklist and came to the conclusion to go to air data computer rev. On the copilot's side [since] the information on that side was erroneous. ATC then assigned us FL210 and during that climb ATC also made us aware of crossing traffic that would be above us at FL220. As we were leveling at FL210 the crossing traffic called that they were receiving and RA and ATC questioned our altitude. Everything showed level FL210; then I switched the copilot out of reversionary mode. At that moment we noticed that the left side and standby showed level at FL210 and that the right side showed us leveling about 180 feet high. We notified ATC that we had a pitot static issue that was causing erroneous altitude and airspeed indications. Basically we were operating where the copilots airspeed was failed; and pilot altitude and standby indications were erroneous (both mfd's also had intermittent altitude comparison monitors). We then proceeded to use ATC to verify level at the remaining assigned altitudes. We contacted our company chief pilot notifying him of the failures and decided to divert to a suitable VMC airport. We continued to check in with each ATC frequency notifying them of the condition we were experiencing and verifying altitudes. We continued without incident and landed safely with the failures continuing all the way to landing.

Google
 

Original NASA ASRS Text

Title: Crew experienced erroneous airspeed indications on the copilot's indicator. Crew was then alerted by ATC and subsequent TCAS Resolution Advisory of deviations from assigned altitude. Crew corrected the altitude deviation with the help of ATC and diverted to a nearby VMC airport.

Narrative: During Takeoff and after V1 we noticed a failure of the copilot's airspeed. This was apparent due to IAS comparison monitor on both MFD's and the copilot's airspeed being completely off from what the left side and standby readouts read. We continued the climb ran the checklist and came to the conclusion to go to ADC Rev. on the copilot's side [since] the information on that side was erroneous. ATC then assigned us FL210 and during that climb ATC also made us aware of crossing traffic that would be above us at FL220. As we were leveling at FL210 the crossing traffic called that they were receiving and RA and ATC questioned our altitude. Everything showed level FL210; then I switched the copilot out of reversionary mode. At that moment we noticed that the left side and standby showed level at FL210 and that the right side showed us leveling about 180 feet high. We notified ATC that we had a pitot static issue that was causing erroneous altitude and airspeed indications. Basically we were operating where the copilots airspeed was failed; and pilot altitude and standby indications were erroneous (both MFD's also had intermittent ALT comparison monitors). We then proceeded to use ATC to verify level at the remaining assigned altitudes. We contacted our company chief pilot notifying him of the failures and decided to divert to a suitable VMC airport. We continued to check in with each ATC frequency notifying them of the condition we were experiencing and verifying altitudes. We continued without incident and landed safely with the failures continuing all the way to landing.

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.