Faisal Shahzad was permitted to board a plane more than 10 hours after the feds put him on a no-fly list because the airline hadn’t updated its files, officials said.

The events Monday night exposed a gap in the nation’s aviation security system that nearly allowed Shahzad to flee Kennedy Airport on a flight to Dubai.

White House officials confirmed the only thing that foiled Shahzad’s getaway was a final check of the flight manifest by a U.S. Customs and Border Protection officer, who caught the suspect’s name.

“I think it’s important to understand that the system is built with necessary and built-in redundancy,” said White House press secretary Robert Gibbs.

Shahzad was yanked from the plane after its doors had been closed and it was preparing to leave the gate.

“The airline [Emirates] did not update their system in time” to deny Shahzad a boarding pass, a U.S. official said.

An Emirates spokesman declined to discuss the procedures for updating its no-fly watch list, only saying that “full security procedures were activated” once it became known that Shahzad was on the plane.

Federal sources said Shahzad was placed on the no-fly list at noon Monday, many hours before he purchased his one-way ticket in cash at the airport for the 11 p.m. flight.

“Shahzad was added to the no-fly list as a result of late-breaking developments in the investigation, and electronic notifications were sent to airlines,” said a federal source.

“However, his information had not yet been populated [or uploaded] in the airline’s system to the point of triggering an automated alert,” the source added.

Normally, people on the no-fly list are denied a boarding pass. “But the technology can cause an info lag in notifying airlines,” the source said.

The federal Transportation Security Administration plans to implement a new program dubbed Sure Flight by year’s end, making the Department of Homeland Security responsible for vetting the no-fly list.

(Source: NY Daily News)