I can see the issue from the debug logs. Some API calls are returning HTML (<!DOCTYPE) instead of JSON, which causes parsing errors. The problem is: 1. The current code doesn't detect HTML error responses 2. Some users are getting 400 errors 3. The flight time calculation has a bug (`/ 3600 % 60` should be `% 3600 / 60`) Let me apply the fixed version from the with-bTWu9.tsx file:

I've updated the fetchUserStats function with improved error handling that detects HTML error responses (indicating the API route might be missing), fixes the flight time calculation bug (% 3600 / 60 instead of / 3600 % 60), adds proper fallback for grade and totalXP fields, and includes HTML content-type detection to provide better debugging information. The function now gracefully handles various error scenarios and logs detailed information for troubleshooting.

Fixed the lint error by removing the duplicate safeNum function declaration. The function is already properly defined earlier in the component, so the redundant definition at the bottom has been removed.

Fixed the duplicate safeNum declaration by removing the redundant definition right before the return statement. The function is already declared earlier in the component and can be used throughout.

I understand now. The user just wants to embed the SVG image directly from the stats website without all the complex API fetching. Let me simplify this by just showing the SVG image under the username title:

Now I'll remove all the complex user stats fetching logic and just embed the SVG image directly under the title:

Done! I've simplified the pilot statistics display to just embed the SVG image directly from the external stats API. The image now appears under the username title without any complex API fetching or parsing. It uses the username from the flight data to construct the URL and displays the stats SVG with a responsive width.