Section 505(q) tightens a citizen petition’s clock

This blog has already drawn the line FDA draws inside a 505(b)(2) application’s own missing right, in what a 505(b)(2) applicant proceeds without, and the line between a biosimilar’s two separate findings, in biosimilarity and interchangeability as different findings. Section 505(q) of the Act names all three pathways — ANDAs, 505(b)(2) applications, and 351(k) biosimilar applications — in a single provision aimed at a different kind of document entirely: a citizen petition filed close enough to one of those pending applications that it could delay the application’s own approval.

Most citizen petitions run on 21 CFR 10.30’s own clock

21 CFR 10.30 lets any interested person petition the Commissioner to issue, amend, or revoke a regulation or order, or to take or refrain from taking any other form of administrative action, and it answers back with a clock of its own: a response within 180 days of receipt. That response doesn’t have to be a final yes or no. The rule lets FDA grant the petition, deny it, or issue a tentative response that explains why the agency hasn’t reached a decision yet, optionally signaling the likely outcome or when a fuller answer might come. Outside observers tracking FDA’s own petition dockets have described that third option as doing most of the real work: a tentative response satisfies the 180-day requirement on its face, which is how a petition can sit open for years without the agency ever missing the deadline the rule actually sets.

A petition that could delay a pending approval moves to a tighter section

Section 505(q) of the Act, added by the FDA Amendments Act of 2007 and tightened by FDASIA in 2012, carves out a narrower case: a citizen petition that requests FDA to take action which could delay approval of a pending ANDA, a 505(b)(2) application, or a 351(k) biosimilar application. FDASIA cut the response deadline for that category from 180 days to 150, and it did something the general rule doesn’t: it barred FDA from extending the 150 days for any reason at all, including the petitioner’s own consent to a later date. A petition that qualifies under 505(q) gets a shorter, harder deadline than an ordinary 10.30 petition, not a longer one.

The certification on the cover page isn’t the same, either

21 CFR 10.30’s own certification — the signed statement that the petition includes all the information and views it relies on, along with any unfavorable representative data the petitioner knows about — explicitly doesn’t apply to a petition covered by 10.31, the regulation FDA finalized in 2016 to implement 505(q). A 505(q)-covered petition carries its own verification statement instead, one that states the specific date the information the petition relies on first became known to the petitioner. That date matters for a reason the general petition never has to answer: it lets FDA, and anyone else reading the docket, see how long the petitioner sat on the information before filing against a pending application’s own clock.

FDA can only use the petition to delay if it says so, in writing

Section 505(q) doesn’t let a pending petition quietly stall an ANDA, 505(b)(2), or biosimilar application by default. The statute requires FDA to approve the application as though the petition didn’t exist unless the agency determines, after reviewing it, that a delay is necessary to protect the public health — and the statute also lets FDA summarily deny a petition it determines was submitted primarily to delay a competitor’s approval. FDA’s own reports to Congress on the provision have repeatedly noted that it has not exercised that summary-denial authority, which leaves the public-health finding as the only lever the statute actually expects FDA to pull on a routine basis.

Whether a petition qualifies isn’t obvious from its own text

None of this applies to every petition that happens to mention a generic drug. The 150-day clock, the barred extension, and the different certification all turn on whether the petition meets 505(q)’s own eligibility test — tied to an actual pending application and a request that could delay it — and a petition that doesn’t meet that test gets the ordinary 180-day treatment regardless of what it argues. That determination is FDA’s own call to make on intake, not something a petitioner’s cover letter gets to settle by asserting it either way.

Where this meets the file

A citizen-petition tracker that files every petition under one undifferentiated 180-day expectation has missed the fork the regulation actually built: which track a petition landed on, the deadline that followed from that determination, and which certification accompanied it. A petition-tracking template that keeps the 10.30-versus-10.31 determination as its own required field, separate from the petition’s substance, is previewed in the launch catalog alongside this week’s other drug-lifecycle templates. If your program tracks that fork differently, the shelf takes that correction directly.