BREAKING Lufthansa A380 at Miami on May 15th 2014, landed below finalfuel reserve
NEWS US Airways flight makes emergency landing after dog poo incident
A woman injured during flight #LH1238 from Frankfurt to Vienna
BREAKING US Airways A320 near Philadelphia on May 22nd 2014, crackedwindshield
Two planes that nearly collided last month at Newark LibertyInternational Airport came within yards of each other, the NationalTransportation Safety Board said
On air traffic control radio captured by the website LiveATC.net, the tower can be heard telling the pilot of the 737 to "go around" and circle the airport.
The controller told the ERJ to watch out for the larger plane on the right.
"Yeah, we were putting the nose down, and, uh, he was real close," the pilot responds.
The 737 flew 135 yards away vertically and 50 yards away laterally from the smaller regional jet.
"We are working with the NTSB in its review of the incident," United spokeswoman Christen David told CNN.
There was no damage to either aircraft or any injuries, according to the NTSB.
The agency will not make a determination of what caused the incident until it releases its final report, which is expected to take months.
NEWS Germanwings A319 near Amsterdam on May 16th 2014, crackedwindshield
BREAKING Second time US Airways A332 turned around and diverted overAtlantic, several crew members ill
BREAKING Part of CityJet aircraft wing became detached mid-air. Flightreturned to London City
More than 60 passengers had to be flown back to London City Airport after part of the plane's wing fell off shortly after it took off
A plane carrying more than 60 people had to turn back after take-off because part of its wing fell off mid-flight.
The pilot had to abort the CityJet flight from London City Airport to Florence, and circle the Thames Estuary before landing again at the airport with a damaged wing.
NEWS US Airways A332 over Atlantic on May 10th 2014, several crewmembers and passengers ill
An airliner nearly collided with a drone in March near an airport inFlorida
Then, Williams segued to a pilot's recent report of "a near midair collision" with a drone near the airport in Tallahassee, Florida. The pilot said that it appeared to be small, camouflaged, "remotely piloted" and about 2,300 feet up in the air at the time of the incident.
"The pilot said that the UAS was so close to his jet that he was sure he had collided with it," Williams said. "Thankfully, inspection to the airliner after landing found no damage. But this may not always be the case."
According to the FAA, the incident took place on March 22 and involved as U.S. Airways Flight 4650 going from Charlotte, North Carolina, to Tallahassee.
Accident: Ariana Afghan B734 at Kabul on May 8th 2014, overran runway
BREAKING U.S. Airways Flight 735 from Philadelphia to Orlando hitsturbulence, 4 hurt
Three people, including two flight attendants, were taken to hospitals for treatment after the plane returned to Philadelphia, said spokesman McGlashen.
There were 265 people on board, including a crew of 10, when the Airbus A330 hit turbulence at about 17,000 feet over Delaware.
Flight 735 was flying from Philadelphia to Orlando at the time of the incident. There had been some reports of light turbulence in the area, but nothing as severe as what the plane ran into.
The Federal Aviation Administration will investigate.
In a separate incident, the wing of a WestJet737 clipped the horizontal stabilizer of aJetBlue plane while on the ground at Orlando International Airport. The horizontal stabilizer is the back set of wings.
The WestJet flight was pushing back from the gate when the incident happened, according to the FAA.
BREAKING Irregularities in #MH370 audio recordings indicate possibleediting, say experts
According to NBC News, the experts said at least two different audio sources recorded the tapes, wherein one of those recordings may have been a digital recorder held up to a speaker.
The Malaysian Transport Ministry on Thursday released a 5-page preliminary report on the missing plane along with the audio recording.
Analysts who listened to the recordings also told NBC that they noticed four clear breaks in the audio that indicated edits, NBC reported.
“It’s very strange,” audio-video forensic expert Ed Primeau of Primeau Forensics was quoted as saying by NBC.
“At approximately 1:14... it sounds like someone is holding a digital recorder up to a speaker, so it’s a microphone-to-speaker transfer of that information. That’s a pretty big deal because it raises the first red flag about there possibly being some editing.”
Primeau and forensic audio examiner Kent Gibson also pointed out other details to NBC on their suspicions.
Gibson said that the tapes indicated that “Malaysian authorities or whoever presented this made edits for whatever reason”.
He added that ”it’s not the way to handle evidence,” but it also did not necessarily imply anything about the investigation.
“Unfortunately, there are no smoking guns, except there are edits. And there are clear edits,” Gibson was quoted telling NBC.
MH370 enroute to Beijing with 239 people from 15 countries on board, disappeared from radar at 1:30am on March 8.
A multinational search was launched to find the missing plane. Investigators think it is somewhere in the southern Indian Ocean, off the west coast of Australia. But so far, all leads and information which have been established through reports and data have yielded nothing. – May 3, 2014.
British Airways flight diverted as passenger gives birth
A flight was forced to make an emergency landing after a passenger went into premature labour and gave birth on board.
The 30-year-old woman, who was 26 weeks into her pregnancy, was one of 296 passengers aboard the British Airways Boeing 777 which was flying from Nigeria to London.
The crew diverted to Palma in Majorca when the woman went into labour. BA crew helped medical staff based at the airport with the birth.
NEWS Malaysia Releases Preliminary Report on Missing Flight #MH370
KUALA LUMPUR, Malaysia—Civilian air-traffic controllers spent precious time in the early hours of March 8 in befuddled exchanges with counterparts in nearby countries after
At the same time, the airline's operation center maintained for more than an hour after the plane went missing that the jet was in "normal condition" and in communication.
KUALA LUMPUR, Malaysia—Civilian air-traffic controllers spent precious time in the early hours of March 8 in befuddled exchanges with counterparts in nearby countries after
At the same time, the airline's operation center maintained for more than an hour after the plane went missing that the jet was in "normal condition" and in communication.
It wasn't until 10:30 a.m.—more than nine hours after the plane vanished—that Defense Minister Hishammuddin Hussein was informed that military radar had tracked the plane turning west toward the Indian Ocean. Mr. Hishammuddin then told Prime Minister
During that stretch, according to the chronology released Thursday, Malaysian and Vietnamese traffic controllers had more than a dozen separate exchanges wondering about the location of the plane and its possible flight path, without any resolution or commencement of a search.
The documents were released on the orders of Mr. Najib in an attempt to bring greater transparency to the search for the missing plane.
The documents lend support to the suspicion that someone intentionally diverted the plane as it crossed from Malaysian to Vietnamese airspace, but offer no new information on what occurred in the cockpit as the plane veered sharply off its flight plan.
They included two maps of the route the plane is believed to have taken, indicating that it flew over the tip of the Indonesian island of Sumatra.
Indonesia, however, has maintained that its radar didn't detect the plane in its airspace.
Agus Barnas, spokesman for Indonesia Coordinating Ministry for Legal, Political, and Security Affairs, said Thursday that two military radar stations in northern Sumatra operate 24 hours a day and would have detected the plane.
"It's impossible that we didn't know if the plane crossed the area," Mr. Barnas said.
The documents also included a two-page summary of air-traffic controllers' conversations, the plane's cargo manifest, the seating chart and audio recordings of five conversations between flight controllers and the cockpit. The documents provide the most comprehensive look yet at what authorities have known for weeks about the plane's disappearance.
More than seven weeks into what has been a fruitless search for remnants of Flight 370, the maps don't clear up questions about the jet's altitude during most of its flight. They also highlight the wide range of speed assumptions investigators used to identify where the jet most likely went down in the Indian Ocean.
Next week, international aviation experts and investigators are planning to meet privately in Canberra in an attempt to further refine estimates of where the plane likely crashed, according to a person familiar with the investigation. The experts, including a panel of air-crash investigators and officials from Boeing Co. and satellite operator Inmarsat PLC, will collectively examine closely guarded military radar data to see whether any new conclusions can be drawn, the person said.
According to the maps released Thursday, investigators calculated the probable area where the plane ran out of fuel based on speeds ranging from about 323 knots to 350 knots. Depending on altitude, that difference could amount to as much as a 716-nautical-mile gap between the "highest-probability area" for wreckage, versus the "lowest" and "mid-probability" areas.
During the last few minutes of the flight before the jet presumably ran out of fuel, the international team of investigators assumed the plane most likely was flying at an altitude of 30,000 feet. But another possible route on the map assumes it was at 15,000 feet.
Once they realized that the Malaysia Airlines aircraft had gone missing, air-traffic controllers in Vietnam and Malaysia spent hours trying to figure out where the plane was, raising questions about whether their counterparts in Cambodia, Singapore, Hong Kong and mainland China had any contact with the jet.
One controller asked the crew of another Malaysia Airlines jet to raise Flight 370 on an emergency radio frequency.
Meanwhile, a Malaysian military radar operator noted that a northbound commercial airliner had turned sharply west over Malaysia. Military radar tracked the plane as it flew for 30 to 40 minutes over the country but the operator didn't alert his superiors because it posed no threat.
Among the documents was a preliminary investigative report submitted earlier to the International Civil Aviation Organization, which Mr. Najib pledged last week to release in an interview with The Wall Street Journal.
The Boeing 777 disappeared March 8 after taking off from Kuala Lumpur to Beijing with 239 people aboard. Based on satellite data, authorities believe the aircraft ended up in the Indian Ocean. No trace of it has been found.
Malaysia has been widely criticized, particularly by relatives of passengers, for not being more forthcoming in providing information about the missing plane.
The aircraft ended communication with air controllers at 1:19 a.m. in Kuala Lumpur but didn't engage with the next control tower in Ho Chi Minh City, Vietnam, as it should have. Moments later, the plane turned west.
"It might be a coincidence, but if you are choosing the one moment in the flight to go dark, that's the moment," said one person familiar with the investigation. "If it is just a mechanical failure, it is an extraordinary coincidence."
It wasn't until 1:38 a.m.—19 minutes later—that controllers in Ho Chi Minh City realized they hadn't heard from Flight 370 and raised the alarm.
Controllers in the two cities communicated back and forth over the next 25 minutes. The Malaysia Airlines operations center then weighed in with information that the plane was in Cambodian airspace.
At 2:15 a.m., a Malaysia Airlines representative informed the Kuala Lumpur air-control center "that MH370 was able to exchange signals with the flight and flying in Cambodian airspace."
Kuala Lumpur questioned whether the plane was supposed to travel through Cambodian airspace; Ho Chi Minh City replied that the planned route was only through Vietnamese airspace.
Over the next few hours, air controllers broadened their search to include Singapore, Hong Kong and Beijing.
Only at 5:30 a.m. did the Kuala Lumpur watch commander initiate search and rescue efforts. The search began in the South China Sea.
After Mr. Najib was notified that the plane was lost, he ordered that a search also begin in the Straits of Malacca, Mr. Hishammuddin said.
The report submitted to the ICAO contains one recommendation: that the U.N. agency consider the safety benefits of real-time tracking for commercial aircraft.
—Daniel Stacey, Andy Pasztor and Joko Hariyanto contributed to this article.
Richard Paddock