Nice idea!
I get an error when logging in (lemm.ee):
The server returned a "500 Internal Server Error".
GlobalMagenta
joined 1 year ago
The flight crew reported that the first officer (FO) was the pilot flying and the captain was the pilot monitoring. The departure from EWR and the cruise segment of the flight were uneventful. Upon arrival at IAH, they were cleared for the DOOBI2 arrival and the ILS 26L approach. According to the flight crew, the airplane was fully configured for landing, on speed and in compliance with the company’s stable approach criteria and the initial touchdown on the main wheels was normal. The FO stated that after the main landing gear touched down, he held aft pressure on the control yoke to keep the nose wheel from hitting the runway; however, the nose wheel made contact with abnormal force. The airplane appeared to bounce, and he reacted by pulling aft on the control yoke, in an effort to keep the nose wheel from impacting the runway a second time. Subsequently, the speed brakes deployed, and the auto brakes engaged which resulted in a second bounce of the nose wheel. He deployed the thrust reversers, and the airplane began to decelerate. The captain assumed control of the airplane and the remainder of the landing rollout was normal with no risk of runway overrun or excursion.
A preliminary review of the flight data recorder (FDR) revealed that after the initial touchdown on both main wheels, the airplane rolled to the left and right main gear lifted off the runway’s surface. Subsequently, the nose wheel touched down with a gravitational force equivalent (g) of about 1.4 g and bounced. The speed brakes deployed, and the nose wheel impacted the runway a second time with a force of about 1.6 g followed by another bounce. The right thrust reverser (TR) deployed, and the nose wheel impacted the runway again with a force of about 1.6 g followed by the deployment of the left TR.
A postaccident examination of the airplane revealed substantial damage to the crown of the upper fuselage.
Agreed. Until I read this post, I was under the impression that it was from the original Reddit-versions developer.
As already suggested, Lemfinity sounds nice!
Yes. This will take some time to repair and re-certify the aircraft (among pressure hull tests). Tailstrike damage is a fairly common type of repair, but this damage is quite extensive and will take some time.
The aircraft is brand new (1.3 years) so the chance of getting repaired is high.
cross-posted from: https://lemm.ee/post/3560055
A Volaris Airbus A321-200N, registration XA-VSC performing flight Y4-488 from Tijuana to Guadalajara (Mexico), landed on Guadalajara's runway 11 at 11:52L (17:52Z) but touched down hard and suffered a tail strike. The aircraft rolled out without further incident. There were no injuries, the aircraft suffered substantial damage.
Mexico's DAAIA (Direccion de Analisis de Accidentes e Incidentes de Aviacion) reported the aircraft XA-VSC suffered a hard landing at Guadalajara, but attributed the aircraft to Viva Aerobus instead of Volaris. The DAAIA quoted the captain of the flight stating: "We were on an ILS approach. The first officer was flying the aircraft, the approach was carried out in a normal way. On short final an instability started, the first officer decelerated the aircraft completely, the aircraft went down, I didn't have time to correct, a strong impact was felt. When we arrived at the apron, we were informed that a tail strike had occurred, a report was recorded in the logbook and the company and authorities were informed." The DAAIA have opened an investigation.
The aircraft is still on the ground in Guadalajara about 72 hours after landing.
A Volaris Airbus A321-200N, registration XA-VSC performing flight Y4-488 from Tijuana to Guadalajara (Mexico), landed on Guadalajara's runway 11 at 11:52L (17:52Z) but touched down hard and suffered a tail strike. The aircraft rolled out without further incident. There were no injuries, the aircraft suffered substantial damage.
Mexico's DAAIA (Direccion de Analisis de Accidentes e Incidentes de Aviacion) reported the aircraft XA-VSC suffered a hard landing at Guadalajara, but attributed the aircraft to Viva Aerobus instead of Volaris. The DAAIA quoted the captain of the flight stating: "We were on an ILS approach. The first officer was flying the aircraft, the approach was carried out in a normal way. On short final an instability started, the first officer decelerated the aircraft completely, the aircraft went down, I didn't have time to correct, a strong impact was felt. When we arrived at the apron, we were informed that a tail strike had occurred, a report was recorded in the logbook and the company and authorities were informed." The DAAIA have opened an investigation.
The aircraft is still on the ground in Guadalajara about 72 hours after landing.
cross-posted from: https://lemm.ee/post/3437085
July 24th - a Delta Airlines Boeing 767-300, registration N189DN performing flight DL-185 from Milan Malpensa (Italy) to New York JFK,NY (USA), was climbing out of Malpensa's runway 35R when the aircraft encountered severe turbulence and hail prompting the crew to declare emergency reporting severe turbulence, hail and a cracked windshield. The crew stopped the climb at FL230 and diverted to Rome Fiumicino (Italy) where the aircraft landed on runway 16R without further incident about 65 minutes after departure. There were no injuries, the aircraft sustained substantial damage including punctures of the right hand wing, punctures of both engine spinners, damage to both engines' fan blades, punctured radome, and dents along the leading edges of the wings.
July 24th - a Delta Airlines Boeing 767-300, registration N189DN performing flight DL-185 from Milan Malpensa (Italy) to New York JFK,NY (USA), was climbing out of Malpensa's runway 35R when the aircraft encountered severe turbulence and hail prompting the crew to declare emergency reporting severe turbulence, hail and a cracked windshield. The crew stopped the climb at FL230 and diverted to Rome Fiumicino (Italy) where the aircraft landed on runway 16R without further incident about 65 minutes after departure. There were no injuries, the aircraft sustained substantial damage including punctures of the right hand wing, punctures of both engine spinners, damage to both engines' fan blades, punctured radome, and dents along the leading edges of the wings.
Also looked for it, but did not find it. I guess it is JetBlue / FAA internal only and only this frame from the clip was released.
Some basic explanation of what it does, how it works and why you think it is great would be nice to hear from an insider :)
Cool! Care to post something on this community with some more explanation? Would love to hear more about it ☺️
Could be. The frame is 32.4 years old. It did get an (extensive) cabin upgrade/refurbishment in January of this year. This could be a contributing factor in repairing the aircraft. A Delta 757-200 also [got a hard landing with a crumpled frame. See the photos. That frame was repaired.
Hahaha, sorry, not a native english speaker. Ofcourse: autobrake. :-)
Correct. It is also used for performance calculations. For example to calculate what Autobreak setting should be used based on the runway length, METAR and landing weight.
I know Airbus aircraft calculate the "EFOB" (End Fuel On Board) in the MCDU. A pilot can calculate the Landing Weight based on the EFOB number by looking at the current weight and calculating based on the EFOB what the landing weight would be.
view more: next ›
It is repairable, but the frame is 34 years old. Frame has got a big cabin refurbishment in January of this year, so that does make the decision harder.