OpenAirDocs.org

20020512011619I

Incident · Minor damage
Open the Markdown

FAA incident report · Israel Galaxy · Baltimore, MD · May 12, 2002

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
May 12, 2002 · 22:00 local
Place
Baltimore, MD
Airport
Martin State Airport
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N408LM
Reported as
Israel Galaxy
People aboard
4
Fatal injuries
0
Pilot’s flight hours
22,000 total75 in this make and model100 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) Pilot spoke to control tower before 10 p.m. to get airport information. Aircraft landed after control tower had closed for the night. Aircraft was observed to still be in the air after it passed its own corporate hangar while landing on runway 15A. Aircraft landed and departed the runway in a right turn and came up on the taxiway. Aircraft went to corporate hangar to be put away and to be inspected. I found out about the incident 2 days later in casual conversation. I spoke with the maintenance personnel and looked over the aircraft and paperwork. The dom has forwarded all paperwork and correspondence between them and the airframe and the engine manufacture overing all there inspections that were performed. Some minor parts were replaced as needed. Complete wheel assemblies were exchanged. All work was done iaw the appropriate manufacturers recommendations. Also found registration paperwork for aircraft not correct. Registration problems were corrected by aircraft registry at okc.

As the FAA filed it

(-23) PILOT SPOKE TO CONTROL TOWER BEFORE 10 P.M. TO GET AIRPORT INFORMATION. AIRCRAFT LANDED AFTER CONTROL TOWER HAD CLOSED FOR THE NIGHT. AIRCRAFT WAS OBSERVED TO STILL BE IN THE AIR AFTER IT PASSED ITS OWN CORPORATE HANGAR WHILE LANDING ON RUNWAY 15A. AIRCRAFT LANDED AND DEPARTED THE RUNWAY IN A RIGHT TURN AND CAME UP ON THE TAXIWAY. AIRCRAFT WENT TO CORPORATE HANGAR TO BE PUT AWAY AND TO BE INSPECTED. I FOUND OUT ABOUT THE INCIDENT 2 DAYS LATER IN CASUAL CONVERSATION. I SPOKE WITH THE MAINTENANCE PERSONNEL AND LOOKED OVER THE AIRCRAFT AND PAPERWORK. THE DOM HAS FORWARDED ALL PAPERWORK AND CORRESPONDENCE BETWEEN THEM AND THE AIRFRAME AND THE ENGINE MANUFACTURE OVERING ALL THERE INSPECTIONS THAT WERE PERFORMED. SOME MINOR PARTS WERE REPLACED AS NEEDED. COMPLETE WHEEL ASSEMBLIES WERE EXCHANGED. ALL WORK WAS DONE IAW THE APPROPRIATE MANUFACTURERS RECOMMENDATIONS. ALSO FOUND REGISTRATION PAPERWORK FOR AIRCRAFT NOT CORRECT. REGISTRATION PROBLEMS WERE CORRECTED BY AIRCRAFT REGISTRY AT OKC.