What Happened at Galt: N361LX on Short Final

November 25, 2022
Final Report
Side view of the crashed Extra EA300/LC showing registration number N361LX; the fuselage is mostly intact but the engine compartment and wings are heavily damaged among trees.
Incident Details
Highest Injury: Fatal
Number of Injuries: 1
City: Wonder Lake
State: Illinois
Aircraft Details
Aircraft Make: Extra
Aircraft Model: EA300
Pilot Name/Operator: N/A
Registration #: N361LX
Departure Airport: 10C
Destination Airport: 10C
Additional Resources
Proudly Sponsored By
Sponsor Logo
Sponsor Logo
Sponsor Logo
Incident Briefing

Setting the Scene
This one took place at Galt Field (10C) in Wonder Lake, Illinois, late on a clear November afternoon. A 2017 Extra EA300/LC, registration N361LX, returned to the pattern after a short local hop. The airplane was on its way back to runway 27 when it descended nearly wings-level into trees about a quarter mile short of the threshold. The engine was running; there was no distress call. The accident happened at 4:15 p.m.—just nine minutes before official sunset—with the sun hanging low and slightly left of the runway centerline. The NTSB ultimately pointed to disorientation from sun glare on final as the key factor.


Pilot and Airplane
The pilot, 75, held a private pilot certificate with airplane single-engine land and sea ratings and an instrument rating. He was not a flight instructor and was seated in the rear seat, as is common in aerobatic two-seat Extras. On his most recent FAA medical application, he reported about 6,200 hours total time, including 50 hours in the prior six months. Investigators could not locate a logbook, so time in type wasn’t available. Toxicology was clean for impairing substances; detected medications (losartan and atorvastatin) are acceptable for pilots. The airplane was an Extra EA300/LC—a high-performance aerobatic tailwheel with a Lycoming AEIO-580 producing 315 horsepower—last inspected in March 2022 and showing about 461 hours total time at that visit.


The Flight
ADS-B data showed the Extra departed runway 27 at 3:58 p.m., climbed to around 3,000 feet MSL, and performed at least two aerobatic maneuvers north-northwest of the field. From there it cruised east toward Antioch, made a 360 over a residential area about 1,250 feet AGL, then turned back toward Galt. Nothing in the track suggested a mechanical issue—just a local outing with some light aerobatics before returning to the pattern.


Rear view of the Extra EA300/LC wreckage showing the damaged tail section and horizontal stabilizer wedged against trees in a forested area.

Into the Pattern
At 4:13:12, the Extra entered the left traffic pattern for runway 27 on the crosswind leg, decelerating through roughly 160 knots calibrated airspeed. Another airplane—a Piper PA-28-181—was already in the pattern. The Piper pilot saw the Extra behind and faster, called him on CTAF, and the Extra confirmed he had the Piper in sight. Between 4:13:45 and 4:14:30, abeam the threshold, the Extra made a 360-degree left turn at about 950 feet AGL—likely for spacing—and then rolled into a descending left base.


The Turn to Final
During that base-to-final sequence, the airplane momentarily slowed to about 70 KCAS and hit a max descent rate near 1,700 fpm. By 4:15:23, the last ADS-B hit was about 0.31 NM from the threshold at approximately 922 feet MSL (roughly pattern altitude at Galt), indicating 84 KCAS, a shallow 2.7-degree left-wing-down roll, and a -6.4-degree flight path angle. Moments later, the airplane’s wings clipped 30- to 40-foot trees almost exactly on the runway 27 extended centerline, about 0.28 NM from the threshold. The wreckage came to rest about 225 feet beyond that initial tree strike, still aligned westbound toward the runway. A witness east of the site heard the engine throughout the descent and then a “wood-chipper” sound—the trees.


Engine and Airframe
The data backs the witness. The engine monitor showed cylinder head temps, EGTs, and fuel flow consistent with power during the last few minutes. EGT for cylinder No. 2 wasn’t recorded on that flight or the previous one, but that’s a data-logging gap, not evidence of a failing jug. Investigators found no preimpact failures in the engine, propeller, or airframe. Flight control continuity for elevator and rudder was confirmed; aileron continuity couldn’t be fully established due to impact damage, but all separations were consistent with overload in the crash sequence. There was fuel at the site and the selector was on the aerobatic (center) tank. In short, nothing mechanical jumped out to explain a loss of control or power.


Wreckage of a red and white Extra EA300/LC airplane lying in a wooded area with broken wings and debris scattered across the ground; yellow caution tape is visible in the background.

Weather, Light, and Geometry
Conditions were VMC: clear skies, 10 miles visibility, light southwesterly wind around five knots. The relevant detail wasn’t the METAR; it was the sun. At the time of the crash, the sun sat about 1.1 degrees above the horizon—essentially on the deck—and 27.5 degrees left of the runway 27 centerline. That lines up with the geometry of the base-to-final turn and short final to 27, where a low, left-forward sun can wash out depth perception and runway cues. Another key data point: the Piper ahead reported being “slightly disoriented” by glare while turning final. That’s an independent pilot, same pattern, same sun angle, same phase of flight.


The Human Factors Thread
If you’ve ever flown a late-day circuit into a west-facing runway, you’ve likely felt this. Sun glare doesn’t just make it hard to see; it messes with your picture. The NTSB cites FAA aeromedical research showing that glare-related accidents cluster in takeoff and landing, with a big portion involving collisions with terrain or objects due to under- or overshooting, or drifting off alignment. In this case, the track, the witness reports, and the wreckage path all tell a consistent story: the Extra remained roughly aligned with the runway and descending, but the pilot did not maintain a safe descent path clear of the tree line on short final. With a bright, low sun on the left, the runway’s threshold environment would have been a low-contrast smear until very late. That’s exactly the kind of scenario where even an experienced pilot can unconsciously continue a slightly low path, expecting to level at the threshold, only to meet trees first.


Close-up of the exposed Lycoming AEIO-580 engine from the Extra EA300/LC wreckage, showing significant impact and fire damage with soil and debris surrounding it.

Why Experience Still Wasn’t Enough
It’s tempting to assume that more hours inoculate us against visual traps, especially in a high-performance machine like an Extra. But experience can also cut the other way: high familiarity can invite confidence in marginal visual cues. The pilot had thousands of hours and was instrument-rated, and nothing in the report suggests poor airmanship earlier in the flight. The energy numbers at the end—84 KCAS, modest bank, negative six-degree flight path—don’t read like an aerobatic mishandling or a stall break; they read like a normal-looking approach that simply stayed low. Add a narrow runway (36 feet wide) and an approach over trees, and you have fewer peripheral references to anchor the glide path when the sun erases contrast.


Safety Takeaways
A few practical lessons stood out for me:

  • Treat late-day west patterns as a risk factor. If the sun is near the horizon and even a few dozen degrees off the nose, move your aim point farther down the runway, add a few knots to stabilize the sight picture, and plan a slightly higher approach until you’re certain you can see the threshold environment. A go-around is cheap—use it at the first twinge of doubt.
  • Use all the tools. If the field has VASI/PAPI, commit to flying it—even if you don’t “need” it. No lights? Consider a wider base, a shallower final turn, and a firm decision gate: if you don’t have the runway environment clearly, go around.
  • Manage spacing assertively. The Extra flew a 360 on downwind for spacing. That was prudent. The next step—ensuring the final segment stays well clear of obstacles—might mean another 360, an early 45-to-downwind break, or simply taking one more lap to let your eyes adjust. Don’t let a mental “I’m set up now” bias push you into an approach that’s hard to see.
  • Know your local obstacles. Many small fields have tree lines short of the threshold. Brief them, especially when the sun angle is ugly. If you operate there often, pre-plan higher visual aim points for late-afternoon landings.
  • Shadow management. Sunglasses help but aren’t magic. A brimmed cap can be a big deal when the sun is skimming the horizon. Use cockpit shading if available and be willing to crane your head to keep the runway out of the worst glare during the turn to final.

The tail section of the Extra EA300/LC, marked N361LX, stored indoors after recovery; the rear fuselage and control surfaces show crushing and tearing from impact.

Closing Thought
This was a capable pilot in a capable airplane on a clear day. The engine was running, the airplane was controllable, and radio calls in the pattern sounded routine. The chain ended not with a system failure but with a visual trap at the worst possible point in the approach. When the sun is low, treat the picture with suspicion. If the runway isn’t crisp, climb, clean up, and try again.

Additional Resources
Proudly Sponsored By
Sponsor Logo
Sponsor Logo
Sponsor Logo
Recent Mishaps
A blue Bell 206B helicopter lies heavily damaged in the front yard of a suburban home. The fuselage is broken open, the tail section is twisted and separated, and debris is scattered across the grass and driveway. A house, trees, and parked cars are visible in the background under clear skies, with police tape marking off the area.

When the Tail Lets Go

If you’ve flown helicopters long enough, you’ve done that short hop after maintenance where you’re tuned into every sound and vibration. That was the plan

Read More »
The wreckage of a red and white airplane is wrapped around a tall tree in a clearing bordered by pine trees. The fuselage is bent and torn, and pieces of the airframe lie scattered nearby.

The Saluda Tree Strike

Setting the StageOn a warm June morning in South Carolina, an RV-9A turned final for Saluda County Airport (6J4). The plan was a straightforward full-stop

Read More »

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Mishaps

A blue Bell 206B helicopter lies heavily damaged in the front yard of a suburban home. The fuselage is broken open, the tail section is twisted and separated, and debris is scattered across the grass and driveway. A house, trees, and parked cars are visible in the background under clear skies, with police tape marking off the area.

When the Tail Lets Go

If you’ve flown helicopters long enough, you’ve done that short hop after maintenance where you’re tuned into every sound and vibration. That was the plan

Read More »

Don’t Miss Out! Get Your FREE Weekly Aviaton Mishap Newsletter!

I promise I will never share your information