NICET FAS-I common mistakes
NICET FAS-I · Understand the traps and how to avoid them.
Treating conductor ampacity as the only check when sizing notification appliance circuits, and skipping the voltage-drop calculation at the last device on the circuit.
Candidates memorize the panel's rated NAC output and the wire gauge table, then assume a circuit that is within ampacity will operate. NICET-style items instead describe a long run with many appliances and expect you to recognize that the end-of-line device sees the lowest voltage and may fall below its listed operating range.
What to do instead
For every NAC question, write out the loop: panel terminal voltage, total load current, resistance per foot for the gauge used, and one-way versus round-trip length. Compute drop to the farthest appliance and compare against its minimum listed operating voltage, not nominal 24 V. Practice with a 2,000-foot 14 AWG run carrying 2 A to see how quickly drop becomes the limiting factor.
Confusing the spacing rules for smoke detectors on smooth ceilings with those for spot-type heat detectors, or applying a flat 30-foot spacing everywhere.
The 30-foot (900 sq ft) figure is widely repeated for smoke detectors, so candidates apply it to heat detectors, corridors, and sloped ceilings alike. Items that give ceiling height, beam pockets, or a corridor width are designed to catch a single-number reflex.
What to do instead
Build a one-page spacing table: smoke detectors on smooth ceilings (30 ft / 900 sq ft), heat detectors by listing and spacing category, corridor requirements, and the 15-foot wall rule. Add a column for ceiling slope and beam depth. Rehearse the logic that reduced spacing applies when height, slope, or obstructions increase detection time.
Selecting a detector technology by habit (ionization for everything, or photoelectric for everything) instead of matching the technology to the expected fire signature described in the item.
Study material often presents ionization and photoelectric as interchangeable, so candidates miss cues like flaming fires, smoldering fires, high airflow, or nuisance sources such as cooking and steam. The item usually embeds the deciding detail in one sentence.
What to do instead
Memorize the pairing: ionization responds faster to small-particle flaming fires; photoelectric responds faster to large-particle smoldering fires. Then practice reading stems for the fire type, ambient conditions, and occupancy. When a stem mentions a kitchen, shower, or dusty space, look for the answer that addresses nuisance alarms rather than raw sensitivity.
Misreading the difference between alarm, trouble, and supervisory signals and how each is annunciated, silenced, and reset.
The three signal types share panel hardware, so candidates blur them under time pressure. Items that describe a closed sprinkler valve, a broken wire, or an activated pull station test whether you can classify the condition before answering the follow-up about silencing or reset.
What to do instead
Make a three-column chart: initiating condition, signal type, required annunciation, and whether silence or reset is permitted while the condition persists. Drill short scenarios until classification is automatic. Remember that supervisory conditions generally cannot be silenced the same way as alarms and that trouble signals indicate impaired protection.
Skipping the sequence-of-operation timeline and answering the activation question from general intuition about what 'should' happen.
Candidates often know individual devices but not the order of events: detection, alarm signal transmission, notification appliance activation, off-premises transmission delay, and waterflow switch timing. Items that ask 'how long until' or 'what activates first' punish guessing.
What to do instead
Write out a default sequence of operation from memory, including any intentional delays for alarm verification and waterflow retransmission, then check it against the code text. Practice converting a narrative description into a timeline with times attached to each step. If an item gives a delay, locate where in the sequence it applies before choosing.
Treating the fire alarm control panel as the only component requiring a battery calculation and forgetting that the calculation must cover standby plus alarm load, including ancillary devices.
Candidates calculate standby current for the panel and call it done, or they use nominal battery voltage without derating for the end-of-life capacity and temperature. Items with a device list and a required standby period are testing the full method, not arithmetic.
What to do instead
Use a fixed worksheet: list every load, its standby current, its alarm current, and its quantity. Sum standby loads for the required period, sum alarm loads for the required alarm duration, add them, then apply the derating factor and temperature correction to size the battery. Redo the calculation with one added notification circuit to see how the answer changes.
Mixing up the roles of the initiating device circuit, the notification appliance circuit, and the signaling line circuit when tracing a fault.
All three are 'circuits' in the panel, and candidates who learned them as vocabulary rather than as topologies cannot tell which devices share a path. An item describing a single open that disables several devices is really asking which circuit topology is in use.
What to do instead
Draw each circuit type: two-wire conventional initiation with end-of-line resistor, four-wire, addressable signaling line circuit as a loop, and notification appliance circuit as a power circuit. Label what a single open or short does to each. Then read fault scenarios and predict which devices are affected before checking the answer.
Answering installation and acceptance-test items from memory of field practice rather than from the documented test procedure, such as testing only a sample of devices or skipping the record of completion.
Experienced candidates rely on habits that pass inspection in their jurisdiction but do not match the test requirements in the exam item. Items about acceptance testing, inspection frequency, and documentation are where field shorthand loses points.
What to do instead
Study the acceptance test sequence as a checklist: plans review, visual inspection, energization, individual device testing, initiating device and notification appliance functional tests, and documentation. Memorize which tests are 100 percent and which may be sampled. Practice writing the test record fields from memory, including device location, type, and result.
Ignoring the difference between protected premises and off-premises signaling, so items about transmission methods, monitoring, and required supervision are answered with the wrong pathway.
Candidates conflate a digital alarm communicator with a supervised dedicated line, or assume any phone or network connection satisfies monitoring requirements. The item usually hinges on whether the pathway is supervised and how failures are annunciated.
What to do instead
Build a comparison of transmission methods: what each uses, whether it is supervised, how a failure is detected and annunciated, and typical backup requirements. For each method, state what happens to the panel when the pathway fails. Then practice scenario items where the question is whether the installation meets supervision requirements, not which technology is newest.
Managing the exam as a pure knowledge test and running out of time or second-guessing correct answers on calculation and code-reference items.
The exam mixes recall, calculation, and code-lookup items, and candidates spend too long on one hard calculation or change answers without a reason. Many items reward a disciplined process more than deep trivia.
What to do instead
Practice with a timer in blocks that mirror the exam, flagging and skipping any item that exceeds a set time budget. For calculations, write the formula before substituting numbers so partial work is visible. For code items, cite the section you are relying on in your scratch notes. Review flagged items only after completing the first pass, and change an answer only when you can name the specific error.