20241108020549I

Incident · Minor damage

FAA incident report · Piper PA-28-161 · Jacksonville, FL · November 8, 2024

Date
November 8, 2024 · 18:34 local
Place
Jacksonville, FL
Airport
Jacksonville International
Phase of flight
Taxi
Operating rules
Pilot school (Part 141)
Operator
ECQS
Damage
Minor damage
Aircraft
N635FT
Reported as
Piper PA-28-161
Reported engine
Lycoming O-320-D3G
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
264 total115 in this make and model13 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.

During taxi out on a night flight, the solo student pilot turned the acft onto an arpt access road and the acft struck a stop sign. He then continued on toward the departure rwy and did not advise jax ATC that anything had happened while taxiing out. The flight then departed at 2334Z with VFR flight following to mlb.

Jax arpt ops called jax twr at 0013Z to advise that the acft may have hit or knocked over a sign in the non-movement area. The twr relayed the message to the student pilot who indicated he was not aware of that happening or any damage to the acft. The acft continued toward mlb with a touch & go ldg at X35 along the way, then landed at mlb without further incident.

A post flight inspection of the acft at mlb by school mx personnel revealed there was minor damage to the rt wing skin leading edge and lower surface located between two wing ribs.

The student plt reported the following to school personnel: he was departing an FBO ramp when he took a turn and realized he was most likely on a ground access road. He didn't see any obstructions, then felt like the acft ran over something on the ground. He thought it was a small item or speed bump, so he tried the brakes, and increased and decreased the RPM to check if there was something on the ldg gear, but everything was normal so he continued the flight and returned to mlb.

As the FAA filed it

DURING TAXI OUT ON A NIGHT FLIGHT, THE SOLO STUDENT PILOT TURNED THE ACFT ONTO AN ARPT ACCESS ROAD AND THE ACFT STRUCK A STOP SIGN. HE THEN CONTINUED ON TOWARD THE DEPARTURE RWY AND DID NOT ADVISE JAX ATC THAT ANYTHING HAD HAPPENED WHILE TAXIING OUT. THE FLIGHT THEN DEPARTED AT 2334Z WITH VFR FLIGHT FOLLOWING TO MLB.

JAX ARPT OPS CALLED JAX TWR AT 0013Z TO ADVISE THAT THE ACFT MAY HAVE HIT OR KNOCKED OVER A SIGN IN THE NON-MOVEMENT AREA. THE TWR RELAYED THE MESSAGE TO THE STUDENT PILOT WHO INDICATED HE WAS NOT AWARE OF THAT HAPPENING OR ANY DAMAGE TO THE ACFT. THE ACFT CONTINUED TOWARD MLB WITH A TOUCH & GO LDG AT X35 ALONG THE WAY, THEN LANDED AT MLB WITHOUT FURTHER INCIDENT.

A POST FLIGHT INSPECTION OF THE ACFT AT MLB BY SCHOOL MX PERSONNEL REVEALED THERE WAS MINOR DAMAGE TO THE RT WING SKIN LEADING EDGE AND LOWER SURFACE LOCATED BETWEEN TWO WING RIBS.

THE STUDENT PLT REPORTED THE FOLLOWING TO SCHOOL PERSONNEL: HE WAS DEPARTING AN FBO RAMP WHEN HE TOOK A TURN AND REALIZED HE WAS MOST LIKELY ON A GROUND ACCESS ROAD. HE DIDN'T SEE ANY OBSTRUCTIONS, THEN FELT LIKE THE ACFT RAN OVER SOMETHING ON THE GROUND. HE THOUGHT IT WAS A SMALL ITEM OR SPEED BUMP, SO HE TRIED THE BRAKES, AND INCREASED AND DECREASED THE RPM TO CHECK IF THERE WAS SOMETHING ON THE LDG GEAR, BUT EVERYTHING WAS NORMAL SO HE CONTINUED THE FLIGHT AND RETURNED TO MLB.

Other reports on N635FT · 2

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