Air Crash
What’s The Story Behind JetBlue’s Nose Gear Incident?

On September 21, 2005, 17 years ago, a JetBlue flight from Burbank to New York City had to make an emergency landing at Los Angeles International Airport. The incident was brought on by the nose gear failing. But what transpired that day? Let’s look at it more.
JetBlue operates flight 292 regularly between Bob Hope Airport in Burbank and John F. Kennedy International Airport in New York. That day, the flight’s aircraft was an Airbus A320-232 with the registration N536JB (Canyon Blue), carrying 140 passengers and six crew members; the aircraft took off normally from Burbank at 15:17, but the pilots noticed they couldn’t retract the landing gear.

They then flew low over Long Beach Municipal Airport (LGB), a JetBlue hub, to allow personnel in the airport’s control tower to inspect the damage to the plane’s landing gear before attempting to land. The nosewheel was discovered to be 90 degrees to the left, perpendicular to the orientation of the fuselage.
Rather than landing at Long Beach Airport (LGB) or turning back to Burbank, the pilot-in-command decided to land at Los Angeles International Airport (LAX) to take advantage of its long, wide runways and modern safety equipment.
The pilots flew the aircraft, which can carry up to 21,260 kg of fuel, in a figure eight pattern for more than two hours between Bob Hope Airport in Burbank and LAX to burn fuel and reduce the chance of fire upon landing. This decision also served to lighten the plane, significantly minimizing possible stress on the landing gear and considering cutting the landing speed. Since the Airbus A320 lacks the mechanical mechanism to dump fuel.

Emergency services and fire engines were waiting on the LAX ramp ahead of the landing. Even though foam trucks were available, they were not deployed. The United States Federal Aviation Administration (FAA) no longer recommends pre-foaming runways, primarily due to concerns that it would deplete firefighting foam supplies that might later be needed to respond to a fire; it is also challenging to determine precisely where a runway should be foamed, and pre-foaming may also reduce the effectiveness of the aircraft’s brakes, potentially causing it to slide off the runway.
The plane touched down on runway 25L, and the nose gear emitted sparks and flames, but the aircraft was undamaged. The pilot-in-command did not employ ground spoilers, reverse thrust, or auto-braking to keep the nose gear off the ground as long as possible. As a result, the plane decelerated more slowly than usual, coming to a stop just 1,000 feet (300 m) from the runway’s end at 18:20. The air traffic control tower reported that there was no fire once the aircraft came to a complete stop, and the passengers deplaned normally through an airstair. No one on board the airplane sustained an injury.

The nose landing gear tires both deflated and tore apart. Despite the unusual nose landing gear arrangement, the plane remained on the runway centerline and continued on its path.

What caused the incident?

The National Transportation Safety Board (NTSB) investigated the incident. The Board determined: Anti-rotation lugs were fractured and separated were discovered during a borescope inspection of the nose wheel assembly.
“The fatigue failure of two anti-rotation lugs due to repeated cyclic pre-landing tests, which allowed the nosewheels to deviate from the 0-degree position on landing gear retraction. A contributing factor was the design of the Brake Steering Control Unit (BSCU) system logic, which prevented the nosewheels from centering. Also contributing was the lack of a procedure to attempt to reset the BSCU system under these conditions.” The National Transportation Safety Board (NTSB)
Airbus released an Operations Engineering Bulletin after the incident. With the help of this technical information, the flight crew reset the brake steering control unit, which regulates the nose landing gear, while in flight.

Sources:
- 16 Years On: What Caused The JetBlue Nose Gear Incident? – Simple Flying
- Cover Image Source: Wikipedia | Andrewmarino
Air Crash
Two Colombian Air Force Pilots Die in Embraer Tucano Aircraft Collision

The Colombian Air Force (FAC) is investigating a tragic accident that occurred during a training mission on Saturday, resulting in the loss of two pilots. Two Embraer T-27 Tucano aircraft collided mid-air and crashed during the exercise in central Colombia. The FAC has not released the identity of the second pilot, and an investigation is underway to determine the cause of the collision.
Video footage of the accident has surfaced on Twitter, showing the aircraft bursting into flames before plummeting to the ground. The FAC confirmed the death of Lieutenant Colonel Mario Andrés Espinosa González, who was in command of one of the Tucano planes. He was scheduled to perform an aerobatic show at this year’s Aeronautical Fair in Rionegro, Antioquia.
Investigation into the Cause of the Collision
The FAC has sent an inspection commission to the crash site to investigate the cause of the accident. The air force expressed condolences to González’s family and colleagues, describing the incident as “unfortunate.”
Preparing for the Aeronautical Fair
The pilots were likely training for the upcoming Aeronautical Fair, which will take place from July 12th to 16th. The FAC had planned to send a squadron of six aircraft, five pilots, a security officer, and five technicians to the event. The Brazilian-built Tucano aircraft have been part of the FAC’s fixed-wing military pilot training program for many years and have logged tens of thousands of safe flight hours.
The squadron was set to perform aerobatic shows ranging from 30 to 35 minutes at the Aeronautical Fair. The FAC had previously announced that the Tucano planes would perform highly complex maneuvers, including inverted flights, 360-degree turns, high-speed crossings, and rapid turns in promotion.

Final Words
The tragic incident has shocked the Colombian Air Force and the aviation community. The cause of the accident remains unknown, and the investigation is ongoing. The loss of the two pilots is a reminder of the risks that military pilots face every day in their service to their country. Our thoughts and condolences go out to their families and colleagues during this difficult time.
Also, you might be interested in reading: Plane Crashes in Virginia After Pilot Passes Out
Air Crash
Plane Crashes in Virginia After Pilot Passes Out

A private jet crashed in a mountainous region in Virginia on June 4th, 2023 after flying over a restricted airspace in Washington D.C. There were no survivors among four people onboard the aircraft.
Details

The plane, a Cessna 560 Citation V, belonged to a company owned by multi-millionaire John Rumpel and was registered N611VG. Rumpel stated that the passengers onboard were his family members, including his daughter and 2-year-old granddaughter.
The aircraft took off at 1:15pm local time from Elizabethton, Tennessee and was en route to Long Island MacArthur Airport in New York when the air traffic controllers lost contact with the pilot. The pilot was unresponsive to calls from air traffic control 15 minutes after departure.
Presumably on autopilot, the private jet flew over its destination at 34,000ft and turned around and started heading back to its origin in a straight line.
During its autopilot cruise back to Elizabethton, the aircraft entered restricted airspace over Washington D.C., which prompted government officials to scramble six F-16 fighters to intercept the aircraft. The F-16 fighters caused sonic booms on the way to intercept the private jet, which alerted many residents over the Washington D.C. area.
Upon reaching the ill-fated private jet, pilots from the F-16 fighter jets observed that the pilot of the private plane was passed out at the controls. The F-16s tried to alert the pilot by firing flares, but all attempts were futile.
The private jet continued cruising towards its origin until it ran out of fuel and crashed into a rural, mountainous region in Virginia.

Cause of the Crash
The FAA and NTSB are currently investigating the incident and have not provided an explanation for the crash; however, it is likely that the plane experienced a loss of cabin pressure shortly after takeoff, as evident by the unconscious state of the pilot. The people onboard would have experienced hypoxia from a lack of oxygen and would have been unaware of the entire event.
Sources:
https://en.wikipedia.org/wiki/2023_Virginia_plane_crash
https://www.cnn.com/2023/06/05/us/virginia-plane-crash-fighter-jets-investigation-monday/index.html
https://www.cbsnews.com/news/plane-crash-virginia-4-died-military-jet-sonic-boom-faa/
Cover Image: NBC News Washington
Air Crash
INCIDENT: Two Airbus A330s Collide on Ground at Tokyo Haneda Airport

On a fateful day at Tokyo’s Haneda Airport, a serious incident occurred involving two Airbus A330 passenger jets. The Japanese transport ministry reported that the Thai Airways Airbus A330-300 (registration HS-TEO) and Eva Air Airbus A330-300 (registration B-16340) collided near a taxiway. The mishap took place as Thai flight #TG683, en route to Bangkok, taxied alongside Eva Air flight #BR189, bound for Taipei. Unfortunately, the incident occurred just before the planes were to line up on runway 16R at Tokyo-Haneda Airport.
The Thai Airways plane sustained noticeable damage, with its winglet appearing to be broken. Fragments from the collision were scattered near the runway, raising concerns about the severity of the impact. In response, authorities from the Tokyo airport office promptly dispatched officials to the scene to investigate the incident thoroughly.

To ensure the safety of all personnel involved and prevent further mishaps, the runway close to the accident site was temporarily closed. Such precautions are crucial in order to assess the situation accurately and prevent any potential hazards that may arise from the damaged aircraft.
As a result of this collision, flight operations at the airport were disrupted, causing delays for several domestic and international flights. Japan Airlines and All Nippon Airways, two prominent airlines operating at Tokyo Haneda Airport, were among those affected by the incident.

Safety remains the top priority, and investigations into the causes and circumstances surrounding the collision are expected to shed light on any lapses or oversights that may have contributed to this unfortunate event.
-
Aviation News10 months ago
Antonov An-225 to be Rebuilt After Being Destroyed in Ukraine
-
Aviation Stories11 months ago
A Boeing 747 Once Flew With 5 Engines
-
Informative11 months ago
Heads-Up-Displays (HUDs) And How It Works
-
Aviation3 years ago
SpaceX’s historic crew launch.
-
Informative2 years ago
Antonov An-225 Mriya: The Plane With 32 Wheels
-
airbus2 years ago
Airbus Beluga vs Boeing Dreamlifter
-
Informative9 months ago
Why Does The Airbus A340 Have 4 Smaller Engines?
-
Informative4 months ago
Why the Airbus A380 Only Utilizes Reverse Thrust on Its Inner Engines