A good place to start.

Explore ballparks and home run landing estimates, compare seating references, and help record where a foul ball or home run actually went. Start by choosing your team. CatchLanding is a beta; the evidence labels tell you what is known.

No account is needed to browse parks, games, maps or ticket links. Sign in free with Google to submit shared observations or issues and keep your profile and favorite teams across devices. A guest draft stays on that browser until you choose to submit it.

Use the team or ballpark search on the home page, open a park, then use Choose a game to select its date and game. For an ongoing game, open Mark a ball. If a game or play is missing, refresh the feed and check the selected date before reporting an issue.

Yes. In Profile & settings, follow multiple teams and choose one default team. You can also edit your username or picture and see your contributions and participation badges.

A dot identifies a recorded or modeled location according to its evidence label. A shaded radius shows uncertainty around an estimate; it is not a guaranteed seat or catch area. Open the ball details to see available player and game information, location stage and source.

Not yet. Some seating, bleachers, renovations and exact numbered-seat coordinates remain under review. Decorative chairs do not establish ticket seat numbers. Use each park’s official seating chart and verify section, row and seat with the seller before buying.

First impact is where the ball first touches a person or surface, including a net. Final spot is where it is caught or comes to rest after any bounces. These are different observations; only mark the stage you actually saw.

Those values alone are not enough: horizontal direction and contact with nets or other surfaces may be missing. Video evidence and fan observations help locate a ball without inventing a precise seat.

No. Estimates and observed samples do not establish a personal catch probability. CatchLanding does not currently publish validated seat-level catch odds or guarantee a catch.

Open Mark a ball, choose the game and event, then select first impact or final spot. Use the 3D park or light map to mark what you saw, review the details, and sign in to submit. If you did not see a location, say so instead of guessing.

Choose Ball hit the net in the reporting flow. Do not force it into a seating section. Record a later catch or resting place separately if you saw it. Physical net coverage and heights vary by park and remain under review.

Use the TV-delay controls and confirm the player and play before marking. If the official play has not arrived yet, use Hold a spot and match it to the correct event when it appears. A held spot is a draft, not a published landing.

Submission does not immediately publish your pin. Reports remain under review; accepted, stage-specific evidence can become public. The collection count and participation badges do not certify a landing. You can find your own contributions in your profile.

Ticket links take you to an external seller. Check the game, section, row, price and seller terms there. Disclosed partner links may provide a referral benefit; a click does not mean a purchase or commission, and sponsors do not buy evidence approval.

Switch to Low resource view in the explorer or the light map in reporting. You can continue comparing sections without loading a full 3D model. On a weak connection, keep your draft and reconnect before submitting.

Open the issue board, check for an existing issue, then submit the park, what happened and what you expected. A screenshot and device/browser information can help. Do not include passwords or private account details.

Open Profile & settings for your own-data export, local drafts and removal-request controls. The Privacy page explains aggregate analytics and the opt-out. A removal request goes through review; it is not an instant deletion button.

The Updates page shows the current release, recent user-facing changes and known work still in progress. The version link in site footers brings you there.