Airways International Cessna 402C incident
Cessna 402C · Incident: airframe, component or system failure during landing
From Grand Bahama International Airport (MYGF) to Fort Lauderdale Hollywood International Airport (FLL)
Event
- NTSB case
- MIA94IA217
- 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
- Incident
- 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
- 0
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 402C
- Aircraft type
- Cessna 402
- 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
- N63PB
- Operator
- Airways International
- Onboard fatalities
- Unknown
- Route
- From Grand Bahama International Airport (MYGF), FREEPORT, OFTo Fort Lauderdale Hollywood International Airport (FLL)
- 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 135: Air Taxi & Commuter
- 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
- Landing · landing roll
- 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
- Minor
Cause areas
- Other crewmember › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FIRST OFFICER FLYING FROM THE LEFT SEAT LANDED SLIGHTLY LEFT OF CENTERLINE ON THE RUNWAY. THE CHECK AIRMAN NOTICED THEY WOULD BE UNABLE TO TURN OFF AT THE DESIGNATED TAXIWAY, AND INSTRUCTED THE FIRST OFFICER TO SLOW DOWN AND CONTINUE THE ROLL OUT TO THE NEXT TAXIWAY. THE FIRST OFFICER STATED HIS BRAKES WERE NOT OPERATING PROPERLY, AND THE AIRPLANE STARTED TO DRIFT TO THE LEFT. THE CHECK AIRMAN STATED, 'I HAVE THE CONTROLS,' BUT WAS UNABLE TO UTILIZE HIS BRAKES DUE TO THE FIRST OFFICER APPLYING BRAKES OVERRIDING THE CHECK AIRMAN'S BRAKES. THE AIRLANE DEPARTED THE RUNWAY 200 FEET FROM THE END OF THE RUNWAY, AND COLLIDED WITH A TAXIWAY LIGHT AND SIGN. EXAMINATION OF THE BRAKE SYSTEM BY THE CHIEF MAINTENANCE INSPECTOR FOR THE AIRLINE, REVEALED THE RETURN SPRING IN THE RIGHT MASTER CYLINDER WAS BROKEN, AND THE LOCK-O-SEAL WAS LEAKING.
Probable cause
The first officer's failure to maintain directional control on landing roll out due to improper use of brakes, resulting in the airplane veering off the runway, and subsequent on-ground collision with a runway light and sign. Contributing to the incident was the failure of the return spring in the right master brake cylinder, and the failure of the first officer to relinquish the flight controls when requested by the pilot-in- command.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA94IA217
- Event ID
- 20001206X02312
- Case number
- MIA94IA217
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 36026305942a471d1da766648c3b283f78ef4f1e1c79673588d0c369485a277d; retrieved 2026-09-18T18:07:52.255Z.
- The NTSB's operator name is blank for N63PB; the operator shown is the name the NTSB's other records give its FAA operator code, FAHA.