FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC93IA084 · Boeing 737-200

6 Jun 1993 · Anchorage, AK, United States

MarkAir Boeing 737-200 · Incident: nose gear collapsed during landing

From Dillingham Airport (DLG) to an unrecorded destination

Report a problem

Event

NTSB case
ANC93IA084
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
General aviation
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

Boeing 737-200

Aircraft type
Boeing 737
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
N673MA
Operator
MarkAir
Onboard fatalities
Unknown
Route
From Dillingham Airport (DLG), Dillingham, AKTo not recorded
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 91: General Aviation
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 · flare/touchdown
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
Nose gear collapsed
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

  • Landing gear, nose gear › Failure, total
  • Landing gear, nose gear › Overload

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

WHILE TAXIING OFF THE RUNWAY AT DILLINGHAM, ALASKA, THE FLIGHT CREW HEARD A 'POP' AND 'GRINDING' SOUND. THE AIRPLANE WAS SUBSEQUENTLY FERRIED TO ANCHORAGE WITH THE NOSE GEAR PINNED IN THE DOWN POSITION. UPON TOUCHDOWN IN ANCHORAGE, THE NOSE GEAR SEPARATED FROM THE AIRPLANE. A METALLURGICAL EXAMINATION OF THE AFFECTED COMPONENTS, PRIMARILY THE NOSE LANDING GEAR INNER CYLINDER, SHOWED THAT THE INNER CYLINDER HAD SEPARATED CLOSE TO THE LOWER END NEAR THE AXLES FOR THE TIRES. VISUAL EXAMINATION OF THE FRACTURE SURFACE WITH THE AID OF A BENCH BINOCULAR MICROSCOPE REVEALED FEATURES TYPICAL OF AN OVERSTRESS SEPARATION INCLUDING CHEVRON MARKS OVER THE MAJORITY OF THE FRACTURE SURFACE AND THE PRESENCE OF A 45 DEGREE FRACTURE PLANE. DURING THE PREVIOUS 12 MONTH PERIOD THERE WERE NO 'HARD' LANDINGS ON RECORD FOR THE AIRPLANE.

Probable cause

THE FAILURE OF THE NOSE LANDING GEAR INNER CYLINDER FROM AN OVERLOAD/OVERSTRESS CONDITION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC93IA084
Event ID
20001211X12495
Case number
ANC93IA084
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1993-06-07.
  • API snapshot SHA-256: 8cdc8a18acde1475c618ba6bc16af58ab69525eb0c1ecb8e6dd9d2685c5ff422; retrieved 2026-09-23T02:00:15.970Z.