Narrative:

Requested 28L for departure as was loaded in the FMC. Tower changed us to 28R as we were holding short of 28L. First officer changed runways in the box; but selected runway 28. There is no runway 28 in sfo. So after lift-off the navigation did not engage for the molen departure. We scrambled to revert to manual navigation procedures to re-establish on the molen departure. This resulted in less than safe operation; we were all trying to figure out what went wrong. Much later in the flight; we saw that there was a runway listed in the sfo runway database that was not at the airport currently shows 28 28L 28R. If you select 28...it will not hook up to the molen. Please fix the database.

Google
 

Original NASA ASRS Text

Title: When changed from Runway 28L to Runway 28R for takeoff; a B747-400 flight crew inadvertently selected Runway 28 in the FMS. After liftoff; LNAV failed to engage because there is no Runway 28 at SFO and the programmed MOLEN SID is compatible only with 28L or 28R.

Narrative: Requested 28L for departure as was loaded in the FMC. Tower changed us to 28R as we were holding short of 28L. First Officer changed runways in the box; but selected Runway 28. There is no Runway 28 in SFO. So after lift-off the NAV did not engage for the MOLEN departure. We scrambled to revert to manual navigation procedures to re-establish on the MOLEN departure. This resulted in less than safe operation; we were all trying to figure out what went wrong. Much later in the flight; we saw that there was a runway listed in the SFO runway database that was not at the airport currently shows 28 28L 28R. If you select 28...it will not hook up to the MOLEN. Please fix the database.

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