An MD11 crew took off into icing conditions. All communication was lost when anti-ice was turned on....

Narrative:

Runway 10 was in use; and the aircraft FMS was set up to use runway 10; as a defined waypoint. After receiving clearance to taxi; ATC issued a clearance to use runway 28. Runway 28 requires defining the location in the FMS; as it is not a runway that is in the database. The captain; the non-flying pilot; defined the runway; entered it and defined other points for the departure. He then taxied out; received takeoff clearance; and I performed the takeoff. Once airborne; we began accumulating ice. The anti-ice equipment was turned on; we lost communication on comm 1 and comm 2. We then noticed that we had no data on our pfd's. The only navigation data available was VOR data. I set up my navigation data for direct to the VOR and followed the flight plan using VOR navigation data and airways. I instructed the captain to update the IRS position over the VOR. This action was performed successfully. What appears to have happened is that the captain entered the wrong coordinates when he entered the runway change. After the coordinates were entered they should have been checked and approved by all crew members. Then the appropriate checklist should have been performed. It is my opinion that the captain should have allowed the flying pilot to modify the flight plan and that all crew members present should have verified the clearance with the data in the FMS; particularly the defined way points. The taxi checklist should have been performed after the changes per our approved procedure.

Original NASA ASRS Text

Title: An MD11 crew took off into icing conditions. All communication was lost when anti-ice was turned on. PFD route data was unavailable. The crew used VOR for navigation and updated the IRS crossing the first VOR.

Narrative: Runway 10 was in use; and the aircraft FMS was set up to use Runway 10; as a defined waypoint. After receiving clearance to taxi; ATC issued a clearance to use Runway 28. Runway 28 requires defining the location in the FMS; as it is not a runway that is in the database. The Captain; the non-flying pilot; defined the runway; entered it and defined other points for the departure. He then taxied out; received takeoff clearance; and I performed the takeoff. Once airborne; we began accumulating ice. The anti-ice equipment was turned on; we lost communication on Comm 1 and Comm 2. We then noticed that we had no data on our PFD's. The only NAV data available was VOR data. I set up my NAV data for direct to the VOR and followed the flight plan using VOR NAV data and airways. I instructed the Captain to update the IRS position over the VOR. This action was performed successfully. What appears to have happened is that the Captain entered the wrong coordinates when he entered the runway change. After the coordinates were entered they should have been checked and approved by all crew members. Then the appropriate checklist should have been performed. It is my opinion that the Captain should have allowed the flying pilot to modify the flight plan and that all crew members present should have verified the clearance with the data in the FMS; particularly the defined way points. The taxi checklist should have been performed after the changes per our approved procedure.

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

Attributes
ACN	993104
Time
Date	201201
Place
Locale Reference	ZZZZ.Airport
State Reference	FO
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Relief Pilot First Officer Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument
Experience	Flight Crew Total 20000 Flight Crew Type 10000
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence

An MD11 crew took off into icing conditions. All communication was lost when anti-ice was turned on. Pfd route data was unavailable. The crew used VOR for navigation and updated the IRS crossing the first VOR.