Learn

Learning preferences

Make learning more comfortable. Changes apply immediately.

Enlarges page content, including diagrams and their labels. You can also use your browser’s zoom.

Choose the colours that are easiest for you to distinguish. Applies to lesson diagrams and lab plots. Labels, shapes, hatching and line patterns also distinguish meanings. Source photographs and raw image brightness stay unchanged; mask-only views are available for image overlays.

ExampleComparisonSample link

Saved in this browser on this device. Preferences are separate from progress backups.

SCIENCE · INVESTIGATE AND EXPLAIN

Find the landing event from the actual initial height

The familiar same-height projectile range formula has a condition: launch and landing heights must match. The supplied virtual point starts 2 m above the ground. Resolve its initial velocity into horizontal vx and vertical vy, with upward positive, then share one elapsed time between both component equations. Horizontal velocity remains constant only because air resistance and other horizontal forces are excluded.

Learning outcome: Compare vx=4 and12 at the same vy, then vy=−2, 0, 4 at vx=8. Retain the accepted root, endpoint and future maximum-height classification. State an observation that would challenge the no-horizontal-force assumption.

Starting recap

Use SI units, signed components, algebraic ratios and graph coordinates. Identify the measurement rule and distinguish a record from an interpolated model.

All lessons are open directly. Your saved experiments remain when you leave and return.

Try

At vy=0, landing time is√0.4≈0.632456 s for any horizontal velocity. Changing vx changes horizontal distance, not fall time under these independent-component assumptions.

Open the experiment

Predict

Does greater horizontal speed keep this ideal point above the ground longer?

Experiment

Compare vx=4 and12 at the same vy, then vy=−2, 0, 4 at vx=8. Retain the accepted root, endpoint and future maximum-height classification. State an observation that would challenge the no-horizontal-force assumption.

Find a ground endpoint without a same-height shortcut

Worked teaching model · synthetic values · Virtual point begins2 m above flat ground with gravity10 m/s² downward and no air resistance. Positive ground-event root ends the model. No physical launch/drop, sport-performance or safety prediction.

Reset keeps your prediction, captures and practice history.

Flight ends at the first ground event

height above ground (m)horizontal position (m)09.186652.799980

Spatial axes use the same pixels per physical unit, preserving geometry. 1: ideal ballistic path (solid). Joined curves show the supplied model, not additional observations.

Equivalent numerical coordinates for Flight ends at the first ground event

ideal ballistic path

horizontal position (m)height above ground (m)
02
0.1148332.05639
0.2296662.11071
0.3444992.16298
0.4593332.21318
0.5741662.26133
0.6889992.30741
0.8038322.35144
0.9186652.3934
1.03352.4333
1.148332.47115
1.263162.50693
1.3782.54065
1.492832.57231
1.607662.60191
1.72252.62945
1.837332.65493
1.952162.67835
2.0672.69971
2.181832.71901
2.296662.73625
2.41152.75143
2.526332.76454
2.641162.7756
2.7562.7846
2.870832.79153
2.985662.79641
3.100492.79923
3.215332.79998
3.330162.79868
3.444992.79531
3.559832.78988
3.674662.7824
3.789492.77285
3.904332.76124
4.019162.74758
4.133992.73185
4.248832.71406
4.363662.69421
4.478492.6723
4.593332.64833
4.708162.6223
4.822992.59421
4.937832.56406
5.052662.53185
5.167492.49758
5.282322.46124
5.397162.42285
5.511992.3824
5.626822.33988
5.741662.29531
5.856492.24868
5.971322.19998
6.086162.14923
6.200992.09641
6.315822.04153
6.430661.9846
6.545491.9256
6.660321.86454
6.775161.80143
6.889991.73625
7.004821.66901
7.119661.59971
7.234491.52835
7.349321.45493
7.464151.37945
7.578991.30191
7.693821.22231
7.808651.14065
7.923491.05693
8.038320.971145
8.153150.883302
8.267990.793399
8.382820.701436
8.497650.607412
8.612490.511328
8.727320.413183
8.842150.312978
8.956990.210712
9.071820.106386
9.186658.88178e-16

At most 82 representative computed coordinates including endpoints; the plotted curve can use a finer grid. A table of a revealed generator is not independent measurement evidence.

Calculated quantities under the declared measurement model
QuantityValueUnit
Positive ground-event time1.14833s
Horizontal landing coordinate9.18665m
Vertical impact velocity-7.48331m/s
Horizontal impact velocity8m/s
Impact speed10.9545m/s
Maximum height during modeled flight2.8m
Time of modeled maximum height0.4s

Solve the vertical ground condition with the actual initial height; horizontal motion shares the same flight time.

The negative quadratic root is not a future landing. For downward initial vertical velocity, maximum height during this modeled flight is the starting2 m, not a past extrapolated apex. At a future apex vy=0 but vertical acceleration remains−10 m/s². Air resistance and finite-size contact are omitted.

Predict before inspecting the values. Save contrasting records with assumptions and one alternative explanation. This virtual display does not certify practical measurement technique.

Solve the vertical ground condition with the actual initial height; horizontal motion shares the same flight time.

The negative quadratic root is not a future landing. For downward initial vertical velocity, maximum height during this modeled flight is the starting2 m, not a past extrapolated apex. At a future apex vy=0 but vertical acceleration remains−10 m/s². Air resistance and finite-size contact are omitted.

Captures preserve recipes and replay their calculated results. They are synthetic model evidence, not physical measurements.

Understand

Begin with a measurement question

The familiar same-height projectile range formula has a condition: launch and landing heights must match. The supplied virtual point starts 2 m above the ground. Resolve its initial velocity into horizontal vx and vertical vy, with upward positive, then share one elapsed time between both component equations. Horizontal velocity remains constant only because air resistance and other horizontal forces are excluded.

Build the algebraic model

The trajectory is x=vxt and y=2+vyt−5t² with g=10 m/s². Landing is the first future solution of y=0. The positive root is [vy+√(vy²+40)]/10; the other root is negative for these controls and does not represent a future event. Multiply the accepted time by vx for the horizontal landing coordinate.

Check a concrete implication

At a future apex, vertical velocity becomes zero while vertical acceleration stays −10 m/s². Horizontal velocity remains nonzero. If vy is initially downward, the maximum height during the modeled future flight is the starting 2 m; an extrapolated earlier vertex is not part of that flight. End the plotted path at contact rather than extending the ideal parabola through the ground.

Challenge the evidence boundary

For vx=8 m/s and vy=4 m/s, flight time is approximately 1.14833 s and horizontal landing coordinate 9.18665 m. Vertical impact velocity is about −7.48331 m/s. The two components determine impact speed, but the model does not describe contact forces, rebound, finite-size objects or practical launch safety. All activity remains virtual.

Worked original case

At vy=0, landing time is√0.4≈0.632456 s for any horizontal velocity. Changing vx changes horizontal distance, not fall time under these independent-component assumptions.

Predict and investigate

Does greater horizontal speed keep this ideal point above the ground longer? Compare vx=4 and12 at the same vy, then vy=−2, 0, 4 at vx=8. Retain the accepted root, endpoint and future maximum-height classification. State an observation that would challenge the no-horizontal-force assumption.

Changed numerical practice

Try the changed case before feedback

A virtual point begins 5 m above ground with vy=0 and vx=6 m/s under g=10. Find horizontal landing distance in metres.

This practice is public and unsaved. A matching number does not verify understanding. Retain your explanation, assumptions and changed-case evidence in the separate course workspace.

Reflect and source-check

Why is zero vertical velocity at the apex not evidence for zero gravity?

Original explanations, synthetic records and models; checked 30 October 2026 against OpenStax College Physics 2e. The guided calculation is algebra-based; no calculus prerequisite is assumed. All activity is virtual. No physical launch, drop, water crossing, machinery operation or medical decision is requested. A public answer or saved capture does not verify independent mastery or actual measurement technique.

Apply

With initial height2 m and initial vertical velocity0, using g=10 m/s², flight time is:

Public practice checks a specific claim. It does not establish independent mastery.

Why is zero vertical velocity at the apex not evidence for zero gravity?

Continue

Completion requires a saved prediction, at least one capture and a reflection. Presence checks do not grade your reasoning.

Skipping retains experiments and awards no mastery.

Save a science backup or import one

Science work is stored locally in this browser, separately from mathematics and AI. It does not sync automatically. Use this science-only backup; this checkout's older all-subject export does not include science.

A legacy file is available only when the complete snapshot fits the 36 MB limit. For larger snapshots, prepare a complete file set below; never discard notebooks to make a smaller file.

Matching imported notebook drafts replace their current drafts. Omitted lessons and known first attempts remain. Export your current work first if you want to retain both drafts.

Complete file sets and course backups

A file set can hold more work than one science file. Keep its manifest and every part together. Each file is limited to 36 MB. This format needs this version of LearnAI or a compatible newer version; older versions can use only the legacy single-file backup above.

The set includes every saved science course and global continuation at this moment. Later edits need a new export. A conflicting tab exports its own visible work, which may differ from saved work in another tab.

0 file(s) selected. File order and filenames do not determine identity. Missing, changed or conflicting parts block the entire restore; no good part is applied by itself.

Science storage: loading. No account or remote computation is required.