Airbus A320-232 incident near Sacramento, California, August 26, 2010
On August 26, 2010 at about 7:51 pm local time, a Airbus A320-232, registered N590JB, suffered minor damage in an incident during approach near Sacramento, California (Sacramento International airport). It was flown under scheduled airline rules (Part 121). 7 people had minor injuries; 84 others were unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The first officer’s inadvertent activation of the parking brake in flight, which led to the airplane abruptly stopping and all four of its main landing gear tires deflating, and his use of a nonstandard procedure to cancel the airplane's monitoring alert system.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 26, 2010 · about 7:51 pm local time · cases in 2010
- Place
- Sacramento, California · Sacramento International · cases near this airport · map
- Type
- Incident
- Injuries
- 7 people had minor injuries; 84 others were unhurt.
- Weather
- visual conditions (good weather)
- Aircraft
- Airbus A320-232 · all A320-232s on the register
- Registration
- N590JB · registry record · serial 2231
- Damage
- Minor damage
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
Upon touchdown and with the first officer as the pilot flying, the airplane rapidly decelerated. After touchdown, air traffic control tower personnel notified the flight crew that smoke and sparks were coming from the airplane's main landing gear. The captain took control of the airplane and maintained directional control as it abruptly came to stop about 2,000 feet from the touchdown point. Postaccident examination of the airplane revealed that all four main landing gear tires were deflated and showed evidence of being locked on touchdown and that the main wheel rims were ground down. According to recorded digital flight data, the parking brake engaged about 5,116 mean sea level and remained engaged throughout the remainder of the flight and landing roll. The data also indicated that the speed brake was activated about 4 seconds before the parking brake. The speed brake lever is on the left side of the center console near the parking brake switch, which is at the bottom center of the console. The first officer stated that he activated the speed brake. It is likely that the first officer inadvertently activated the parking brake at the same time. The flight crew stated that they were unaware of any indications or warnings related to the parking brake system during flight. The airplane's Electronic Centralized Aircraft Monitoring (ECAM) system should alert the flight crew when the parking brake is engaged in flight. However, after the accident, the first officer stated that he selected and held down the ECAM emergency cancel pushbutton for several seconds and that this was his typical procedure to preempt the autopilot disconnect audio. This action also terminated, in part, most of the visual alert indications associated with the in-flight parking brake activation. (The alerts would appear in the cancelled caution field on the status page and could be recalled, if necessary.) The operator's procedures state to only use the ECAM emergency cancel pushbutton to suppress spurious master cautions. A review of the airplane's cockpit voice recorder transcript revealed no audible autopilot disconnect or parking brake activation warnings. Examination of the airplane's parking brake and ECAM revealed no mechanical malfunctions or failures that would have precluded normal operation. If the first officer had not cancelled out most of the visual alert indications associated with the in-flight parking brake activation, it is likely that a visual warning would have alerted the flight crew to the in-flight parking brake activation.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Miscellaneous/other during approach defining event
- Miscellaneous/other during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Copilot
- cause Personnel issues › Action/decision › Action › Incorrect action selection › Copilot
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 8,716 hours in all; 4,397 in this make and model; 240 in the last 90 days; 79 in the last 30 days; 4,874 as pilot in command; 1,241 on instruments
- Last flight review: October 31, 2009
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: airline transport pilot, flight instructor
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 9,100 hours in all; 2,217 in this make and model; 279 in the last 90 days; 91 in the last 30 days; 5,264 as pilot in command; 1,431 on instruments
- Last flight review: September 17, 2009
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 25,986 hours
- Last inspection: continuous airworthiness programme, August 26, 2010
- Maximum gross weight: 170,735 lb
- Seats: 160
- Landing gear: retractable
- Engine 1: Iae V2527-A5 (turbofan); 0 hours total
- Engine 2: Iae V2500SERIES (turbofan); 0 hours total
- Operator: Jetblue Airways CORP
The flight
- Departed from: LGB Long Beach CA at 6:41 pm
- Destination: SMF Sacramento CA
- Flight plan: IFR
- Runway 16R, 8,600 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 170° at 13 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 55°F (13°C)
- Altimeter: 29.85 inHg
- Observation at 7:53 pm from SMF
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 3 | |||
| Flight crew | 2 | |||
| Passengers | 7 | 79 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
17 documents, released by the NTSB on January 7, 2014. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N590JB on the register today · the tail number may have moved to another aircraft since
- Airbus A320 789 registered today · the model family and its accident history
- Airbus 1,503 aircraft on the register
- Engine: Iae V2527-A5 113 aircraft carry this series today · as the NTSB recorded it
- Engine: Iae V2500SERIES 262 aircraft carry this series today · as the NTSB recorded it
- Sacramento International · nearest airport
- Long Beach (Daugherty Field) · departed from
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR10IA430.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
