Narrative:

Departed ZZZZ runway 12R via SID. ZZZZ is not in the FMC database so we followed the guidance in B747 aom 04.11.01.02 departure or destination airport not in the FMC database. With SID waypoints entered as latitude/longitude coordinates our plan was to fly the initial SID heading to 1480 feet and then fly direct to the coordinates of [the] fix in LNAV. We insured that all waypoint altitude and speed constraints were in the FMC and we performed the takeoff in heading and VNAV as we had briefed and we were all comfortable with the plan. The autopilot was engaged at approximately 1100 feet MSL and as we approached 1480 feet the pm (pilot monitoring) selected direct to [fix] and the fix dropped out of the FMC; thereby eliminating the speed and altitude constraints. The pm requested vectors to zzzzz; a fix later in the SID. Because the altitude and speed constraints were deleted; the aircraft leveled approximately 200-300 feet high and accelerated above the 205 knot restriction. I saw the altitude deviation and before I could correct it; ATC issued us a higher altitude. We were climbing to altitude in VNAV and navigating to zzzzz in LNAV when ATC queried us as to which SID we were assigned. No further discussions with ATC occurred. Prior to departure from ZZZZ1; I spoke with a dispatcher about the destination not being in the database and he too was unfamiliar with the aom guidance. All three crewmembers have never been introduced to nor trained in the concepts and procedures of operating into or out of non-database airports. The aircraft ICAO flight plan designated the aircraft as a fully capable pbn (performance-based navigation) aircraft. The aom procedure does not contain any guidance as to whether or not RNAV procedures should be accepted and as a crew we made assumptions regarding aircraft navigation capabilities which were incorrect. We assumed that once the waypoints were entered in latitude/longitude format aircraft pbn capabilities were normal. Upon departure from ZZZZ; we had a very short taxi to the departure runway. Communication is always challenging. We were the only english speakers on clearance; ground; tower and departure frequencies during a fairly busy time of day at ZZZZ. If we are to be operating at non-database airports; these procedures need to be addressed during initial and recurrent training events. I think the [flight plan] should contain a note in the remarks section alerting crews to the additional requirements for operations at non-database airports. There is a NOTAM buried in the briefing papers but it needs to be more prominent.

Google
 

Original NASA ASRS Text

Title: Boeing 747-400 Flight Crew reported exceeding altitude and airspeed RNAV departure constraints due to FMC temporary malfunction.

Narrative: Departed ZZZZ Runway 12R via SID. ZZZZ is not in the FMC database so we followed the guidance in B747 AOM 04.11.01.02 Departure or Destination Airport Not in the FMC Database. With SID waypoints entered as latitude/longitude coordinates our plan was to fly the initial SID heading to 1480 feet and then fly direct to the coordinates of [the] fix in LNAV. We insured that all waypoint altitude and speed constraints were in the FMC and we performed the takeoff in heading and VNAV as we had briefed and we were all comfortable with the plan. The autopilot was engaged at approximately 1100 feet MSL and as we approached 1480 feet the PM (Pilot Monitoring) selected direct to [fix] and the fix dropped out of the FMC; thereby eliminating the speed and altitude constraints. The PM requested vectors to ZZZZZ; a fix later in the SID. Because the altitude and speed constraints were deleted; the aircraft leveled approximately 200-300 feet high and accelerated above the 205 knot restriction. I saw the altitude deviation and before I could correct it; ATC issued us a higher altitude. We were climbing to altitude in VNAV and navigating to ZZZZZ in LNAV when ATC queried us as to which SID we were assigned. No further discussions with ATC occurred. Prior to departure from ZZZZ1; I spoke with a dispatcher about the destination not being in the database and he too was unfamiliar with the AOM guidance. All three crewmembers have never been introduced to nor trained in the concepts and procedures of operating into or out of non-database airports. The aircraft ICAO flight plan designated the aircraft as a fully capable PBN (Performance-Based Navigation) aircraft. The AOM procedure does not contain any guidance as to whether or not RNAV procedures should be accepted and as a crew we made assumptions regarding aircraft navigation capabilities which were incorrect. We assumed that once the waypoints were entered in latitude/longitude format aircraft PBN capabilities were normal. Upon departure from ZZZZ; we had a very short taxi to the departure runway. Communication is always challenging. We were the only English speakers on clearance; ground; tower and departure frequencies during a fairly busy time of day at ZZZZ. If we are to be operating at non-database airports; these procedures need to be addressed during initial and recurrent training events. I think the [flight plan] should contain a note in the remarks section alerting crews to the additional requirements for operations at non-database airports. There is a NOTAM buried in the briefing papers but it needs to be more prominent.

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.