Arithmetic Progressions: Clean Setup for Any FE Sequence Problem

aₙ = a₁ + (n-1)d. You’ve seen this formula before, maybe even used it in earlier courses.

But when the FE problem says “find the sum of the first 18 terms” and you’re holding that nth term formula, the pause hits—do I need this formula, or do I need the series formula instead?

That hesitation is where problems dealing with arithmetic progressions break down.

Not because the math is conceptually hard, but because “find term 18” and “find the sum of the first 18 terms” sound similar enough under pressure that you’re not certain which formula protects you until you’ve already committed to one.

Arithmetic progressions show up when costs escalate at a fixed rate per period, when distances increase uniformly, or when any engineering quantity grows or declines by the same amount each step.

The pattern is simple—each term differs from the previous by a constant value.

The challenge is translating “total combined length” or “sum of payments” into the correct formula when both options feel plausible.

This guide walks you through a systematic approach that works on any arithmetic progressions problem the FE throws at you—from finding a specific term to calculating series sums to working backward from given terms to find the formula.

You’ll learn exactly which formula to use based on what the problem asks for, how to extract a₁ and d without sign errors, and how to verify your setup matches the question before you calculate.

Before we walk through it step by step, watch this short video.

It shows you the full process from identifying the sequence type to selecting the right formula to executing the calculation.

You’ll see exactly where students typically confuse term value with series sum—and how to avoid that trap by reading what they’re actually asking for before you write anything down.

Why Arithmetic Progressions Feel Messy on the FE

Arithmetic progressions are straightforward in concept—each term increases or decreases by the same amount.

But that clarity disappears when the problem asks you to find term 18 of a sequence that starts at -7 with a common difference of 2.5, and you’re not sure if you plug in n = 18 or n = 17, or whether the formula accounts for the fact that the first term is already given.

Here’s what happens in real time:

• You read the problem and recognize you are working with arithmetic progressions because the differences are constant
• You write down aₙ = a₁ + (n-1)d but you’re not confident whether to use the term formula or the sum formula
• You extract a₁ but you’re second-guessing whether the sequence actually starts at term 1 or if there’s an offset
• You calculate d by subtracting terms but you flip the order and get the wrong sign
• Or the problem gives you terms and asks for the sum, and you use the term formula instead because you didn’t read carefully

The friction comes from three places: formula selection ambiguity when the wording doesn’t explicitly say “find the nth term” versus “find the sum,” parameter extraction uncertainty when a₁ or d aren’t immediately obvious from how the sequence is presented, and verification gaps where you solve correctly but answer the wrong question because you didn’t confirm what they actually asked for.

This isn’t a lack of math ability. It’s a structure problem.

The workflow below removes the ambiguity and gives you a repeatable process that handles any arithmetic progressions the FE puts in front of you.

What Is an Arithmetic Progression?

Arithmetic progressions are a sequence of numbers where the difference between any two consecutive terms is constant.

That fixed difference is called the common difference, denoted d.

In practical terms, if you’re tracking costs that rise by $500 each year, distances that increase by 3 meters per interval, or temperatures that drop by 2 degrees each hour, you’re working with arithmetic progressions.

The sequence 4, 7, 10, 13, 16 is an arithmetic progression with a₁ = 4 and d = 3.

Think of it like climbing stairs where every step is exactly the same height.

You know exactly where you’ll be after 10 steps because the height gain per step never changes.

Arithmetic progressions work the same way—each term is just the previous term plus d, so if you know where you start and how much you’re adding each time, you can find any term or the total of all terms without listing them out.

On the FE Exam, arithmetic progressions show up when they describe a linear cost escalation, a repeating increment in design parameters, or when they hand you a sequence and ask you to find a specific term or sum the series.

The test isn’t checking whether you understand what “constant difference” means—it’s checking whether you can translate their wording into the correct formula and execute without mixing up parameters.

The key is recognizing that there are only two things they can ask: what is term n (use the term formula), or what is the sum of the first n terms (use the series formula).

Once you know which question you’re answering, the rest is parameter extraction and arithmetic.

Breaking Down Arithmetic Progressions Step by Step

Problems dealing with arithmetic progressions break when you extract a₁ and d correctly but apply the term formula when they asked for the sum—or vice versa.

The numbers are right, the arithmetic is clean, but you answered a different question than what they actually asked.

This happens because both types of problems present the same way: they give you a sequence with constant differences, tell you the first term and how it changes, and ask for a value.

The distinction between “find the 12th term” and “find the sum of the first 12 terms” gets blurred when you’re reading fast.

The workflow below removes that ambiguity.

It forces you to decide what you’re solving for before you touch a formula, then walks you through parameter extraction with verification built in.

Three steps, same process every time, regardless of how the sequence is presented or what the wording looks like.

Let’s lay it out.

Step 1: Read the problem and identify what they’re asking for

The first thing you need to do is read the problem statement carefully and determine whether they want a specific term (like “find the 12th term”) or a sum (like “find the sum of the first 12 terms”).

This is the decision that determines which formula you’ll use.

If they ask for a term, you’re using aₙ = a₁ + (n-1)d.

If they ask for a sum, you’re using Sₙ = (n/2)(a₁ + aₙ).

As you read, watch for wording variations.

They might say “the value of term 10,” “the 10th element,” or “aₙ when n = 10″—those all mean use the term formula.

They might say “the sum of the first 10 terms,” “the total value through term 10,” or use summation notation—those all mean use the series formula.

Step 2: Extract a₁ and d from the sequence

Now that you know what formula you need, extract the first term a₁ and the common difference d.

If the sequence is given explicitly (like 5, 8, 11, 14…), then a₁ is just the first number in the list and d is the difference between any two consecutive terms.

Calculate d by taking (second term) – (first term), or any term minus the one before it.

If the sequence is given as a formula (like aₙ = 3 + 2n), you can find a₁ by plugging in n = 1, and you can find d by calculating a₂ – a₁.

If they describe the sequence in words (like “a sequence starts at 12 and increases by 4 each term”), then a₁ = 12 and d = 4.

Make sure you get the sign of d correct. If the sequence is decreasing, d will be negative.

Step 3: Apply the appropriate formula and solve

With a₁, d, and n identified, substitute them into the correct formula.

If you’re finding a specific term, use aₙ = a₁ + (n-1)d.

Plug in your values, do the arithmetic, and that’s your answer.

If you’re finding a sum, you need aₙ first (use the term formula to find it if they didn’t give it to you), then use Sₙ = (n/2)(a₁ + aₙ).

Plug in n, a₁, and aₙ, calculate, and that’s the sum.

Work through the arithmetic carefully.

The math is simple but sign errors or order of operations mistakes will give you a wrong answer that’s close enough to a distractor to feel right.

Example Problem: Arithmetic Progressions

The workflow handles any arithmetic progressions setup.

The key is identifying what they’re asking for, extracting parameters cleanly, and applying the correct formula.

Right now, we’re going to work through an FE-style problem so you see exactly how this plays out under real conditions.

The goal is clean structure—speed will come after a few reps.

With that laid out, let’s put these steps into practice.

This problem states:

Solution: Arithmetic Progressions

When you see “the total combined length of the first 15 components,” the question isn’t whether you can add 15 numbers together—it’s whether you recognize “total” as the signal for series sum (requiring Sₙ formula) versus thinking “15 components” means you need the 15th term value (requiring aₙ formula).

That single word “total” determines which formula protects you from answering the wrong question.

The workflow removes that uncertainty.

It forces you to identify what they’re asking before you select a formula.

Let me walk you through this step by step, the same way I would across the table.

Step 1: Read the problem and identify what they’re asking for

The first thing we need to do is read the problem statement carefully and determine whether they want a specific term or a sum.

They say “the total combined length of the first 15 components.”

The word “total” combined with “first 15 components” tells us we’re summing multiple terms, not finding a single term.

So we need the series sum formula: Sₙ = (n/2)(a₁ + aₙ).

This means we’ll need to identify n (the number of terms), a₁ (the first term), and aₙ (the 15th term).

Step 2: Extract a₁ and d from the sequence

Now we extract the first term and the common difference.

The problem states: “The first component is 8.2 cm long”—that’s a₁.

a₁ = 8.2 cm

They also tell us: “each subsequent component is 1.5 cm longer than the previous one”—that’s d.

d = 1.5 cm

We know we’re summing the first 15 components, so n = 15.

Before we can use the series formula, we need aₙ, which in this case is a₁₅.

We’ll use the term formula to find it.

aₙ = a₁ + (n-1)d

a₁₅ = 8.2 + (15-1)(1.5)

a₁₅ = 8.2 + (14)(1.5)

a₁₅ = 8.2 + 21

a₁₅ = 29.2 cm

Step 3: Apply the appropriate formula and solve

With n = 15, a₁ = 8.2, and a₁₅ = 29.2, we now plug into the series sum formula.

Sₙ = (n/2)(a₁ + aₙ)

S₁₅ = (15/2)(8.2 + 29.2)

S₁₅ = (7.5)(37.4)

S₁₅ = 280.5 cm

So the final answer to this problem is C) 281 cm.

This tells us that the total combined length of the first 15 components, when each component increases by 1.5 cm starting from 8.2 cm, sums to 280.5 cm.

The answer choice of 281 cm is the closest value, accounting for rounding in the problem setup.

Common Mistakes to Avoid on Arithmetic Progressions Problems

These are the five mistakes that turn arithmetic progressions from automatic points into wrong answers that look right until you check your work.

Mistake 1: Using the term formula when they asked for the sum

You see “find the value for the first 15 components” and you read “15 components” and immediately think you need a₁₅, so you use aₙ = a₁ + (n-1)d and calculate 29.2 cm.

But they didn’t ask for the 15th component—they asked for the total combined length of all 15 components.

You answered a completely different question, and even though your arithmetic was perfect, you picked a distractor that matches what a₁₅ would be.

This happens because the word “components” appears in both types of questions.

“Find the 15th component” uses the term formula.

“Find the total length of 15 components” uses the series formula.

The difference is whether they want one specific value or a sum.

Mistake 2: Extracting the wrong sign for d

You calculate the common difference by subtracting consecutive terms, but you subtract in the wrong order and get d = -1.5 when it should be d = 1.5, or vice versa.

This happens when you grab two consecutive terms and do (earlier term) – (later term) instead of (later term) – (earlier term), and the sign flips.

In our example, if you calculate d = 8.2 – 9.7 instead of d = 9.7 – 8.2, you get d = -1.5 when the sequence is actually increasing.

A sequence that increases has a positive d.

A sequence that decreases has a negative d.

If you calculate d and it doesn’t match the direction the sequence is actually moving, you extracted it wrong—and every calculation after that compounds the error.

Mistake 3: Confusing a₁ with n or starting at the wrong term

The problem gives you a sequence like 8.2, 9.7, 11.2, 12.7 and asks for the 15th term, and you use n = 15 but you accidentally use a₁ = 9.7 because that’s the second number in the list and it’s visually prominent.

Or the sequence doesn’t start at term 1—it starts at term 0 or some other offset—and you don’t account for that when you plug into the formula.

This breaks the entire calculation because every term after a₁ depends on having the correct starting value.

In our manufacturing example, if you use a₁ = 9.7 instead of a₁ = 8.2, you’ll calculate a₁₅ = 30.7 cm instead of 29.2 cm, and your series sum will be off by over 20 cm.

Mistake 4: Forgetting to find aₙ before using the series formula

You need to calculate Sₙ = (n/2)(a₁ + aₙ), and you have a₁ and n, but you don’t have aₙ yet.

You either skip it and use n in place of aₙ, or you freeze because you’re not sure how to find aₙ.

The series formula requires the last term.

If they don’t give it to you directly, you have to calculate it using the term formula first: aₙ = a₁ + (n-1)d.

Then you plug that result into the series formula.

In our example, we had to find a₁₅ = 29.2 cm before we could calculate S₁₅.

Without that step, there’s no way to use the series formula correctly.

Mistake 5: Arithmetic errors in simple multiplication or addition

You set up the problem correctly, extract all parameters correctly, use the right formula, but then you calculate (15/2)(8.2 + 29.2) and make an arithmetic mistake in the multiplication or addition.

You get 275 when the answer is 280.5, or you misalign decimal places, or you add wrong.

The error isn’t conceptual—it’s execution under time pressure.

This happens when you’re moving fast and you skip writing intermediate steps because “it’s just arithmetic.”

In our example, if you calculate 8.2 + 29.2 = 37.2 instead of 37.4, your final sum will be 279 cm instead of 280.5 cm, and you’ll pick the wrong answer choice.

Rules of Thumb for Arithmetic Progressions Problems on the FE

The workflow handles formula selection.

These checkpoints protect each step from the execution errors that happen when you’re moving fast and “find the sum of 15 terms” starts to blur with “find the 15th term.”

• Read the question twice before choosing a formula: If they ask for “the nth term” or “the value of term n,” use aₙ = a₁ + (n-1)d. If they ask for “the sum of the first n terms” or “total combined length,” use Sₙ = (n/2)(a₁ + aₙ). The word “sum” or “total” is your signal for the series formula. In our manufacturing example, “total combined length of the first 15 components” meant series sum, not the 15th term. Don’t assume—confirm which question they’re asking before you write anything.
• Always verify d by checking the second term: After you calculate d, add it to a₁ and make sure it equals the second term in the sequence. In our example, a₁ = 8.2 and d = 1.5, so the second term should be 8.2 + 1.5 = 9.7. If it doesn’t match, you either subtracted in the wrong order or misidentified a₁. This two-second check catches sign errors before they propagate through the entire calculation.
• If you need aₙ for the series formula, find it first: The series formula Sₙ = (n/2)(a₁ + aₙ) requires the last term. If they don’t give it to you, calculate it using the term formula before you attempt the sum. In our example, we had to find a₁₅ = 29.2 cm before we could calculate S₁₅ = 280.5 cm. Write it as a separate step—don’t try to substitute the term formula directly into the series formula in your head. That’s where arithmetic errors happen.
• Check the direction of the sequence against the sign of d: If the sequence is increasing (each term is larger than the last), d must be positive. If the sequence is decreasing, d must be negative. In our manufacturing example, components increased from 8.2 to 9.7 to 11.2, so d = +1.5. If your calculated d doesn’t match the direction the sequence is actually moving, you made an error in extraction. Fix it before you go further.
• Write down what you’re solving for before you start: Before you substitute anything, write one sentence: “I’m finding the 15th term” or “I’m finding the sum of the first 15 terms.” This forces you to confirm you’re answering the right question. If you can’t write that sentence clearly, reread the problem—you’re not ready to start calculating yet.

Final Thoughts | Arithmetic Progressions

Every problem presenting arithmetic progressions hinges on one decision: are they asking for a specific term value, or are they asking for the sum of multiple terms?

Get that right, and the rest is parameter extraction and arithmetic.

Get it wrong, and you’ll calculate 29.2 cm when they wanted 280.5 cm—or vice versa—because you answered a different question than what they actually asked.

This isn’t a math difficulty problem.

You can calculate aₙ = a₁ + (n-1)d and Sₙ = (n/2)(a₁ + aₙ) without issue.

The breakdown happens in the first ten seconds, when you’re reading “find the total combined length of the first 15 components” and deciding whether “total” means sum or whether “15th component” is what they want.

The workflow removes that fragility.

It forces you to identify what you’re solving for before you touch a formula.

Step 1 isn’t “extract a₁ and d”—it’s “read the problem and determine: term or sum?”

Once you make that call cleanly, the rest is mechanical.

The mistakes you’ve seen—using the term formula when they asked for sum, flipping the sign on d, forgetting to find a₁₅ before calculating S₁₅—all stem from rushing that initial decision or not verifying your parameters against the sequence itself.

The rules of thumb protect you: verify d produces the second term, confirm you’re answering the question asked, write down what you’re solving for before you calculate.

Arithmetic progressions are clean points when you execute systematically.

You don’t need special tricks or memorization beyond two formulas.

You need to identify which formula matches what they’re asking, extract a₁ and d without sign errors, and verify your setup before you calculate.

The difference between students who get these right and students who miss them isn’t mathematical ability—it’s reading precision.

The students who get them right confirm what the question asks before selecting a formula.

They don’t rely on instinct.

They follow the workflow, verify their d value matches the sequence direction, and check they’re solving for the right output.

You’ve got that process now.

Take it, practice it on FE problems until the decision between term and sum becomes automatic, and turn arithmetic progressions into points you bank without second-guessing.

Want more targeted practice? Our full library of FE problems and guides is waiting here.

You know what’s holding you back.

It’s not practice problems—you can find those anywhere.

It’s the lack of a clear plan that tells you exactly what to study, when to study it, and how to know you’re actually ready.

That’s the gap between effort and results.

Between hours logged and real progress.

Prepineer closes that gap: a personalized FE prep roadmap that adapts to your schedule, targeted practice on what the exam actually tests, and real coaching support when you’re stuck—so every hour you invest builds exam-day confidence, not just hope.

Start your free 7-day trial and see what focused prep feels like.