All rules

An arrival before its departure

arrival-before-departureon by defaultJapanese / English

A flight or a train in an itinerary that arrives before it departs

Example

Flagged
- 1:30 PM Flight AA 2177 (departs Washington 1:30 PM, arrives Boston 1:05 PM)
What chaff prints
1:70 Arrives at 1:05 PM, before it departs at 1:30 PM
Fixed
- 1:30 PM Flight AA 2177 (departs Washington 1:30 PM, arrives Boston 3:05 PM)
What chaff prints
no finding

How to fix

Check both times and correct the wrong one. If the leg arrives on the next day, mark the arrival "+1" or "next day".

Why it matters

When a leg such as "departs Washington 1:30 PM, arrives Boston 1:05 PM" arrives before it departs, one of the times is wrong. The reader has to look the connection up again, and someone may plan around the wrong time. A departure and an arrival in one line are compared: times marked "departs" and "arrives" (or "dep" and "arr"), and the departure and arrival columns of a table. An arrival marked as the next day (+1, "next day") gets a day added, and when both times have a date, the dates are compared first.

What it does not flag

An arrival marked as the next day (+1, "next day"), a pair where only one time has a date, and a line with two different time zones or a "local time" mark (the times cannot be compared as written) are not reported.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: arrival-before-departure — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax arrival-before-departure --why "reason"
Turn it off for the team (chaff.yaml)
rules: arrival-before-departure: off
Technical details
Layer
L3
Status
stable
Severity
warning
Languages
Japanese and English
Suited to
business, technical, blog, legal, docs, academic, literature, speech
Reads from the document
dates

Levels

Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).

stricterror
normalwarning
relaxedinfo

This rule has no limit to count to. A level sets how a finding is marked: relaxed keeps the finding and marks it a step lower.

By genre

Runs by default in
technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes, legal/contract, legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, speech/address, speech/transcript
Turned off by the genre in
literature/fiction, literature/essay, literature/poetry, literature/play

Genres

Message

Arrives at {arrival}, before it departs at {departure}

This page is built from the rule's definition file:packages/chaff/rules/arrival-before-departure.yaml