FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Pinnacle Airlines Flight 2823

11 Mar 2005 · Milwaukee, WI, United States

Bombardier CL-600-2B19 · Accident: airframe, component or system failure en route

From LaGuardia Airport (LGA) to General Mitchell International Airport (MKE)

Report a problem

Event

NTSB case
CHI05FA077
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Bombardier CL-600-2B19

Aircraft type
Bombardier CL-600
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N8932C
Onboard fatalities
Unknown
Route
From LaGuardia Airport (LGA), New York, NYTo General Mitchell International Airport (MKE), Milwaukee, WI
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The Part 121 scheduled domestic passenger flight received substantial damage when it veered off the left side of runway 1L during landing. The flight had departed LaGuardia International Airport en route to Milwaukee International Airport (MKE). During climbout through Flight Level 20 (20,000 feet), the No. 1 Hydraulic Low Pressure caution light illuminated. The flight crew ran the Quick Reference Handbook (QRH) checklist for the caution message. The procedures outlined in the QRH instructed the flight crew to: "Land at the nearest suitable airport." The captain informed the airline's maintenance control about the caution message, but he did not inform flight dispatch about the caution message or the need to land at the nearest suitable airport. The flight continued to its destination airport. The flight was cleared to land on runway 1L. The winds were 290 degrees at 10 knots. The captain reported that the landing was normal until the airplane started to veer off the left side of the runway. The post accident inspection of the airplane revealed no preexisting anomalies, other than the loss of the No. 1 Hydraulic system which resulted in the loss of ground spoilers. The NTSB Aircraft Performance Study indicated that the airplane approached runway 1L crossing the threshold at about 2302:16 at a recorded radio altitude of about 50 feet above ground level, with an indicated airspeed of 139 knots (about 136 knots ground speed) and a pitch angle of about 4 degrees nose down. The airplane began to drift right of centerline by about 20 feet, and touchdown occurred at a calculated distance of 2,400 feet beyond the runway threshold in a crab angle of about 5 degrees nose left relative to the ground track, and at a roll angle of about 1 degree left bank angle. The lateral load at touchdown was recorded at -0.2 G's. After touchdown, the airplane's ground track continued to drift right of centerline about 25 feet while the airplane nose remained to the left of the ground track. The airplane's ground track then began to turn left and departed off the side of the runway (veered off the runway) at about 2302:37 and approximately 4,200 feet beyond the threshold. The longitudinal acceleration from point of touchdown to when it veered off the runway was recorded between -0.12 and -0.15 G's. An investigation of airport operations revealed that airport operations did not inspect Runway 1L/19R after a pilot report (PIREP) of NIL braking action by a Beech Jet at 2018. Airport operations did not conduct or provide friction measurement reports and (Notices to Airmen) NOTAMS for Runway 1L/19R between March 10 at 1925 and the time of the accident on March 11 at 2302, when airport conditions were changing with significant snowfall accumulations. The airport did not conduct a runway inspection or friction report of Runway 1L/19R after the airplane veered off the runway.

Probable cause

the captain's failure to adequately compensate for the crosswind conditions, and his failure to maintain directional control during landing. Contributing factors include the captain's failure to land at the nearest suitable airport after an in-flight mechanical problem, the airport operation's failure to conduct runway friction tests and to issue NOTAMS in accordance with existing regulations, the crosswind, the snow-covered runway, the runway sign, and night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05FA077
Event ID
20050317X00323
Case number
CHI05FA077
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-03-12.
  • API snapshot SHA-256: 1c94efc6319cbe340ae675e0e8ec7b865d3c33dd43a04e8a0a4f7025951a1e86; retrieved 2026-09-18T15:04:21.334Z.