# Accident 19980605024389A: Cessna 310K, Miami, FL, June 5, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 5, 1998, 16:15 local time
- Place: Miami, FL
- Airport: Opa Locka Airport
- Damage: Substantial damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 25.9091° N, 80.2692° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=25.9091&lon=-80.2692&mi=10
- Aircraft: N366J, a cancelled registration (https://openairdocs.org/deregistered/N366J-2008-09-16) (OpenAirDocs)
- Registry model: Cessna 310K (registry code 2074228, https://openairdocs.org/model/cessna-310k) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 310K
- Reported engine: CONT IO520E
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,043 total, 361 in this make and model, 11 in the last 90 days
- NTSB investigation: [NTSB MIA98LA192](https://openairdocs.org/ntsb/MIA98LA192) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980605024389A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

UNKNOWN TO PILOT AN EXPLOSION HAD OCCURRED IN LEFT WING. FUEL LEAK CHAGED BATTERY CABLE ARCED. BURNED HOLE IN WING. (.4)DURING TAKEOFF AN EXPLOSION INSIDE THE LEFT WING RESULTED IN A SHORT DURATION FIRE.  THE FLIGHT CONTINUED AND LANDED UNEVENTFULLY.  THE UPPER AND LOWER WING SKINS WERE DISPLACED AND FIRE DAMAGE WAS NOTED AFT OF THE BATTERY BOX.  THE POSITIVE BATTERY CABLE WAS CHAFING AGAINST AN OPEN ADEL CLAMP LOCATED NEAR THE BATTERY BOX; THE PK SCREW WAS NOT IN PLACE.  ARCHING WAS NOTED ON THE BATTERY CABLE.  TESTING OF THE LEFT AUXILIARY FUEL TANK REVEALED SEEPAGE FROM THE FUEL TANK VENT LINE.  THE FUEL TANK WAS NOT PROPERLY SECURED INSIDE THE WING.  DAMAGE TO THE EXTERNAL PORTION OF THE AUXILIARY FUEL TANK NEAR THE VENT LINE WAS NOTED.  PREVIOUS FUEL SEEPAGE FROM THE LEFT WING AUXILIARY FUEL TANK WAS EVIDENT IN THE FORM OF DAMAGE ON THE GROUND BENEATH THE LEFT WING AREA GREATER THAN DAMAGE TO THE GROUND BENEATH THE RIGHT WING AREA.  ALSO, A WAX TYPE RESIDUE WAS FOUND ON THE LOWER WING SKIN IN THE AREA OF THE FUEL SEEPAGE.  THE SERVICE MANUAL INDICATES TO CHECK ELECTRICAL CABLES FOR CONDITION EVERY 100 HOURS.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB MIA98LA192](https://openairdocs.org/ntsb/MIA98LA192), Jun 5, 1998: Cessna 310K (N366J), Opa-Locka, FL, substantial damage. Probable cause: The fuel leak due to improper installation of the left auxiliary fuel tank by maintenance personnel. Also, inadequate annual inspection of the airplane by maintenance personnel for failure to…

## Other reports on N366J (3)

Matched to the same aircraft by N-number and date.

- [Incident 20020609025329I](https://openairdocs.org/incident/20020609025329I), Jun 9, 2002: Cessna 310K (N366J), Champaign-Urban, IL, Substantial damage. (-23) [privacy data omitted] pilot was cleared for touch and go while performing patern work. Pilot selected gear down but did not get nose gear safe…
- [Incident 20000204020989I](https://openairdocs.org/incident/20000204020989I), Feb 4, 2000: Cessna 310K (N366J), Jacksonville, FL, Minor damage. (-23)Craig tower (crg) issued N366J clearence to land on runway 23 but instructed pilot to make a go-around when it was apparent that the landing gear was not…
- [Incident 19920810037139I](https://openairdocs.org/incident/19920810037139I), Aug 10, 1992: Cessna 310K (N366J), Tampa, FL, Minor damage. Electrical failure en route. Elected to land at airport with inoperable lights. Struck runway sign. No NOTAM issued

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.